🚀 Features
Section titled “🚀 Features”Allow assigning ids for pipelines manually
Section titled “Allow assigning ids for pipelines manually”Mar 3, 2025 · @dominiklohmann · #5026
The /pipeline/create and /pipeline/launch endpoints now accept an optional
id parameter for assigning the pipeline’s ID manually.
🐞 Bug Fixes
Section titled “🐞 Bug Fixes”Fix crash in the MSB in merging mode
Section titled “Fix crash in the MSB in merging mode”Mar 3, 2025 · @IyeOnline · #5028
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.
Make UDO resolution order-independent
Section titled “Make UDO resolution order-independent”Mar 3, 2025 · @dominiklohmann · #5029
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.
Fix tls option of to_splunk
Section titled “Fix tls option of to_splunk”Feb 28, 2025 · @jachris · #5027
Using the tls option of the to_splunk operator no longer directly emits an
error.
Fix startup delay in from_fluent_bit
Section titled “Fix startup delay in from_fluent_bit”Feb 28, 2025 · @dominiklohmann · #5025
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.
Make drop not remove empty records
Section titled “Make drop not remove empty records”Feb 27, 2025 · @dominiklohmann · #5021
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 {}.