Releases: tenzir/tenzir
Tenzir Node v5.1.3
This patch release features the following improvements and bug fixes over Tenzir Node v5.1.2:
- User-defined operators still required the
// tql2comment at the start or thetenzir.tql2option to be set, despite TQL2 being the default since Tenzir Node v5.0. They now work as expected. - The
tableoption of theto_azure_log_analyticshas been renamed tostreamto better reflect the expected value. Additionally, a new optionbatch_timeouthas been added to configure the max duration to wait before finishing a batch. - The
encode_urlanddecode_urlfunctions encode and decode URLs. For example,"Hello%20World".decode_url()returnsb"Hello World". - We added a new
strictoperator that takes a pipeline and treats all warnings emitted by that pipeline as errors, i.e., effectively stopping the pipeline at the first diagnostic. This is useful when you to ensure want a critical piece of your pipeline does not continue in unexpected scenarios.
Tenzir Node v5.1.2
This patch release features the following improvements and bug fixes over Tenzir Node v5.1.1:
- The
export,metrics,diagnosticsandpartitionsoperators returned an empty result when used before the node had successfully loaded its persisted data. They now wait correctly. - We fixed a very rare bug that on shutdown could mark running pipelines as stopped, completed, or failed, causing the pipelines not to restart alongside the node.
- The node no longer refuses to start when its last shutdown happened in the brief period on startup after its PID file was created and before it was flushed.
- The
to_google_cloud_loggingoperator is now available in both Docker and static builds. The operator had earlier been missing due to a configuration issue. - We split the
nameoption ofto_google_cloud_logging, no longer requiring user to construct the ID manually.
Tenzir Node v5.1.1
This patch release features the following improvements and bug fixes over Tenzir Node v5.1:
- The
movekeyword now works as expected for the first positional argument of themapandwherefunctions. - The
to_google_cloud_loggingoperator was not available in static binary builds due to an oversight. This is now fixed.
Tenzir Node v5.1
Tenzir Node v5.1 adds more flexible ways to access and move fields, bitwise functions, and a native integration with Google Cloud Logging.
Discover Tenzir Node v5.1
📣 Dive into the details of Tenzir Node v5.1 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, and explore the demo node with just a few clicks and a guided tour.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL).
📝 Read all the details in our changelog.
Tenzir Node v5.0.1
This patch release features the following improvements and bug fixes over Tenzir Node v5.0:
- The
chart_*operators no longer sort y-axes by their names. Instead, the user-provided order is used. For example, inmetrics "pipeline" | chart_bar x=timestamp, resolution=1d, y={"Ingress": ingress.bytes.sum(), "Egress": egress.bytes.sum()}the field order is now "Ingress" followed by "Egress" as specified instead of the other way around. - We fixed a bug that caused demo nodes to shut down after 30s.
- We fixed multiple bugs that caused unexpected internal failures and the creation of potentially empty
Tuples in ClickHouse. - The
to_clickhouseoperator now supportsblobs, which will be sent as anArray(UInt8).
Tenzir Node v5.0
Tenzir Node v5.0 makes TQL2 the default and only option throughout Tenzir.
Discover Tenzir Node v5.0
📣 Dive into the details of Tenzir Node v5.0 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, and explore the demo node with just a few clicks and a guided tour.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL).
📝 Read all the details in our changelog.
Tenzir Node v4.32.1
This patch release adds two small improvements over Tenzir Node v4.32:
- The default max request size has been changed from 4 MiB to 1 MiB for
to_google_secopsto align with Google's API. While the API documentation states a limit of 4MiB per request, in practice the limit turned out to be 1 MiB. - The
to_google_secopsoperator now has two additonal configuration options to set themax_request_sizeand thebatch_timeout.
Tenzir Node v4.32
Tenzir Node v4.32 brings an all-new integration with Google SecOps and new language features for accessing record fields while suppressing warnings if the fields don't exist.
Discover Tenzir Node v4.32
📣 Dive into the details of Tenzir Node v4.32 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, and explore the demo node with just a few clicks and a guided tour.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL).
📝 Read all the details in our changelog.
Tenzir Node v4.31.2
This patch release adds two small improvements over Tenzir Node v4.31.1:
- We removed the limit of 20,000 elements in lists and records for
read_*operators andparse_*functions. - We added compression support in the
to_hiveoperator.
Tenzir Node v4.31.1
This patch release fixes an internal bug that prevented Docker images from being uploaded for the Tenzir Node v4.31 release. It contains no functional changes.