Vector v0.43.0 release notes

VRL was updated to v0.20.0. This includes the following changes:

Breaking Changes & Upgrade Guide

• Fixes the to_float function to return an error instead of f64::INFINITY when parsing non-normal numbers. (https://github.com/vectordotdev/vrl/pull/1107)

New Features

• The decrypt and encrypt VRL functions now support aes-siv (RFC 5297) encryption and decryption. (https://github.com/vectordotdev/vrl/pull/1100)

Enhancements

• decode_punycode and encode_punycode with the validate flag set to false should be faster now, in cases when input data needs no encoding or decoding. (https://github.com/vectordotdev/vrl/pull/1104) Otherwise, it will return None. (https://github.com/vectordotdev/vrl/pull/1117)
• The encode_proto function was enhanced to automatically convert valid string fields to numeric proto fields. (https://github.com/vectordotdev/vrl/pull/1114)

Fixes

• The parse_groks VRL function and Datadog grok parsing now catch the panic coming from rust-onig on too many regex match retries and handle it as a custom error. (https://github.com/vectordotdev/vrl/pull/1079)
• encode_punycode with the validate flag set to false should be more consistent with when validate is set to true, turning all uppercase character to lowercase as well as doing punycode encoding (https://github.com/vectordotdev/vrl/pull/1115)
• Removed false warning when using set_semantic_meaning. (https://github.com/vectordotdev/vrl/pull/1148)

Allows for chunked GELF decoding in message-based sources, such as UDP sockets or unix datagram sockets. Implementation is based on Graylog’s documentation. The implementation also supports payload decompression.

This framing method can be configured via the framing.method = "chunked_gelf" option in the source configuration.

The elasticsearch sink now supports publishing events as bulk “update"s by configuring bulk.action to update. While using this mode has a couple of constraints:

1. The message must be added in .doc and have .doc_as_upsert to true.
2. id_key must be set, and the encoding field should specify doc and doc_as_upsert as values

Expose connection_retry_options in the Pulsar sink configuration to allow customizing the connection retry behaviour of the pulsar client. This includes the following options:

• min_backoff_ms: Minimum delay between connection retries.
• max_backoff_secs: Maximum delay between reconnection retries.
• max_retries: Maximum number of connection retries.
• connection_timeout_secs: Time limit to establish a connection.
• keep_alive_secs: Keep-alive interval for each broker connection.