Tenzir v4.19.2

This patch release contains the following bug fixes and improvements over Tenzir v4.19:

Tenzir v4.19.2

• The subscribe operator now delivers metrics more consistently.
• The throttle operator allows for limiting the bandwidth of a pipeline.
• We've made some changes that optimize Tenzir's memory usage. Pipeline operators that emit very small batches of events or bytes at a high frequency now use less memory. The serve operator's internal buffer is now soft-capped at 1Ki instead of 64Ki events, aligning the buffer size with the default upper limit for the number of events that can be fetched at once from /serve. The export, metrics, and diagnostics operators now handle back pressure better and utilize less memory in situations where the node has many small partitions. For expert users, the new tenzir.demand configuration section allows for controlling how eagerly operators demand input from their upstream operators. Lowering the demand reduces the peak memory usage of pipelines at some performance cost.

Tenzir v4.19.1

• We fixed a problem where a stoppingpython operator could cause a crash.
• The python operator is now compatible with Python 3.9 again.
• The AMQP connector now handles connections with heartbeats correctly.
• We restored the performance of the partitions operator to pre --experimental-include-ranges times, when the flag is not used.

Tenzir v4.19.1

This patch release contains the following bug fixes and improvements over Tenzir v4.19:

Tenzir v4.19.1

• We fixed a problem where a stoppingpython operator could cause a crash.
• The python operator is now compatible with Python 3.9 again.
• The AMQP connector now handles connections with heartbeats correctly. Thank you @satta!
• We restored the performance of the partitions operator to pre --experimental-include-ranges times, when the flag is not used.

Tenzir v4.19

With the new Tenzir 4.19 release you can now write and deploy packages, enjoy the benefits of the improved python operator, and use the buffer operator to control back pressure.

Discover Tenzir v4.19

📣 Dive into the details of Tenzir v4.19 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🎓 Learn more by following the getting started guide and user guides.
💭 Understand why Tenzir was developed and how it measures up against the competition.
📝 Read all the details in our changelog.

Tenzir v4.18.5

This patch release contains the following bug fixes and improvements over Tenzir v4.18:

Tenzir v4.18.5

• The unflatten operator now correctly preserves field order and overwrites in case of a name conflict.

Tenzir v4.18.4

• The subscribe operator no longer propagates back pressure to its corresponding publish operators when part of a pipeline that runs in the background, i.e., is not visible on the overview page on app.tenzir.com. An invisible subscriber should never be able to slow down a publisher.

Tenzir v4.18.3

• Fixed an issue where null records were sometimes transformed into non-null records with null fields.
• We fixed an issue that sometimes caused subscribe to fail when multiple publish operators pushed to the same topic at the exact same time.
• We fixed a bug that caused a potentially unbounded memory usage in export --live, metrics --live, and diagnostics --live.
• metrics export now includes an additional field that shows the number of queued events in the pipeline.

Tenzir v4.18.2

• We fixed a memory leak in export that was introduced with v4.18.1.

Tenzir v4.18.1

• We fixed a bug that caused deduplicate <fields...> --distance <distance> to sometimes produce incorrect results when followed by where <expr> with an expression that filters on the deduplicated fields.
• Pipelines that use the every modifier with the export operator no longer terminate after the first run.
• Setting the tenzir.endpoint option to false now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes or tenzir processes to connect.

Tenzir v4.18.4

This patch release contains the following bug fixes and improvements over Tenzir v4.18:

Tenzir v4.18.4

• The subscribe operator no longer propagates back pressure to its corresponding publish operators when part of a pipeline that runs in the background, i.e., is not visible on the overview page on app.tenzir.com. An invisible subscriber should never be able to slow down a publisher.

Tenzir v4.18.3

• Fixed an issue where null records were sometimes transformed into non-null records with null fields.
• We fixed an issue that sometimes caused subscribe to fail when multiple publish operators pushed to the same topic at the exact same time.
• We fixed a bug that caused a potentially unbounded memory usage in export --live, metrics --live, and diagnostics --live.
• metrics export now includes an additional field that shows the number of queued events in the pipeline.

Tenzir v4.18.2

• We fixed a memory leak in export that was introduced with v4.18.1.

Tenzir v4.18.1

• We fixed a bug that caused deduplicate <fields...> --distance <distance> to sometimes produce incorrect results when followed by where <expr> with an expression that filters on the deduplicated fields.
• Pipelines that use the every modifier with the export operator no longer terminate after the first run.
• Setting the tenzir.endpoint option to false now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes or tenzir processes to connect.

Tenzir v4.18.3

This patch release contains the following bug fixes and improvements over Tenzir v4.18:

Tenzir v4.18.3

• Fixed an issue where null records were sometimes transformed into non-null records with null fields.
• We fixed an issue that sometimes caused subscribe to fail when multiple publish operators pushed to the same topic at the exact same time.
• We fixed a bug that caused a potentially unbounded memory usage in export --live, metrics --live, and diagnostics --live.
• metrics export now includes an additional field that shows the number of queued events in the pipeline.

Tenzir v4.18.2

• We fixed a memory leak in export that was introduced with v4.18.1.

Tenzir v4.18.1

• We fixed a bug that caused deduplicate <fields...> --distance <distance> to sometimes produce incorrect results when followed by where <expr> with an expression that filters on the deduplicated fields.
• Pipelines that use the every modifier with the export operator no longer terminate after the first run.
• Setting the tenzir.endpoint option to false now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes or tenzir processes to connect.

Tenzir v4.18.2

This patch release contains the following bug fixes and improvements over Tenzir v4.18:

Tenzir v4.18.2

• We fixed a memory leak in export that was introduced with v4.18.1.

Tenzir v4.18.1

• We fixed a bug that caused deduplicate <fields...> --distance <distance> to sometimes produce incorrect results when followed by where <expr> with an expression that filters on the deduplicated fields.
• Pipelines that use the every modifier with the export operator no longer terminate after the first run.
• Setting the tenzir.endpoint option to false now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes or tenzir processes to connect.

Tenzir v4.18.1

This patch release contains the following bug fixes and improvements over Tenzir v4.18:

Tenzir v4.18.1

• We fixed a bug that caused deduplicate <fields...> --distance <distance> to sometimes produce incorrect results when followed by where <expr> with an expression that filters on the deduplicated fields.
• Pipelines that use the every modifier with the export operator no longer terminate after the first run.
• Setting the tenzir.endpoint option to false now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes or tenzir processes to connect.

Tenzir v4.18

Monitoring Tenzir nodes is easier than before with Tenzir v4.18 and its new health metrics.

Discover Tenzir v4.18

📣 Dive into the details of Tenzir v4.18 from our insightful announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🎓 Learn more by following the getting started guide and user guides.
💭 Understand why Tenzir was developed and how it measures up against the competition.
📝 Read all the details in our changelog.

Tenzir v4.17.4

This patch release contains the following bug fixes and improvements over Tenzir v4.17:

Tenzir v4.17.4

• We fixed a bug that caused a "Bad file descriptor" error from the python operator, when multiple instances of it were started simultaneously.
• We fixed a bug that changed the state of managed pipelines to completed on node shutdown.
• We fixed an assertion caused by failing configured pipelines with retry on error enabled.

Tenzir v4.17.3

• We fixed a bug in Tenzir v4.17.2 that sometimes caused the deletion of on-disk state of configured contexts on startup.
• The partitions [<expr>] source operator supersedes show partitions (now deprecated) and supports an optional expression as a positional argument for showing only the partitions that would be considered in export | where <expr>.

Tenzir v4.17.2

• We fixed a bug that very rarely caused configured pipelines using contexts to fail starting up because the used context was not available, and similarly to fail shutting down because the used context was no longer available before the pipeline was shut down.
• We fixed an issue where diagnostics were not properly propagated and thus not available to the diagnostics operator.

Tenzir v4.17.1

• We fixed a bug in Tenzir v4.17 that caused some nodes to error on startup with an "unreachable" error.