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 correspondingpublish
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 withnull
fields. - We fixed an issue that sometimes caused
subscribe
to fail when multiplepublish
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
, anddiagnostics --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 withv4.18.1
.
Tenzir v4.18.1
- We fixed a bug that caused
deduplicate <fields...> --distance <distance>
to sometimes produce incorrect results when followed bywhere <expr>
with an expression that filters on the deduplicated fields. - Pipelines that use the
every
modifier with theexport
operator no longer terminate after the first run. - Setting the
tenzir.endpoint
option tofalse
now causes the node not to listen for node-to-node connections. Previously, the port was always exposed for other nodes ortenzir
processes to connect.