Skip to content

Tenzir Node v4.29.1

Download the release on GitHub.

Allow assigning ids for pipelines manually

Section titled “Allow assigning ids for pipelines manually”

The /pipeline/create and /pipeline/launch endpoints now accept an optional id parameter for assigning the pipeline’s ID manually.

By @dominiklohmann in #5026.

Dropping all fields from a record with the drop operator no longer removes the record itself. For example, from {x: {y: 0}} | drop x.y now returns {x: {}} instead of {}.

By @dominiklohmann in #5021.

We fixed a bug in the read_xsv and parse_xsv family of operators and functions that caused the parser to fail unexpectedly when the data contained a list (as specified through the list separator) for fields where the provided schema did not expect lists.

By @IyeOnline in #5028.

Using the tls option of the to_splunk operator no longer directly emits an error.

By @jachris in #5027.

The resolution of user-defined operator aliases in the tenzir.operators section is no longer order-dependent. Previously, an operator foo may have depended on an operator bar, but not the other way around. This limitation no longer exists.

By @dominiklohmann in #5029.

We fixed a bug that caused pipelines with from_fluent_bit to not report their startup successfully, causing errors when deploying pipelines starting with the operator through the Tenzir Platform.

By @dominiklohmann in #5025.

Last updated: