Release notes

7.16.3-26.5

Improvements

  • Upgraded to Elasticsearch version 7.16.3.

7.16.2-26.4

Bug fixes

  • Fixed an issue that prevented the execution of an msearch request containing joins on the same index with different algorithms.

7.16.2-26.3

Improvements

  • Upgraded to Elasticsearch version 7.16.2. This Elasticsearch release includes fixes for CVE-2021-45105. For more information, please refer to ESA-2021-31.

7.16.1-26.2

Improvements

  • Upgraded to Elasticsearch version 7.16.1. This Elasticsearch release includes fixes for CVE-2021-44228 and CVE-2021-45046. For more information about these vulnerabilities, refer to ESA-2021-31.

7.15.2-26.1

Improvements

  • Upgraded to Elasticsearch version 7.15.2.

7.15.1-26.0

Improvements

  • Upgraded to Elasticsearch version 7.15.1.

  • Introduced vectorization of the project phase to increase throughput, including:

    • Refactoring of tuple processing into pipelines for all join algorithms and all data types.

    • Reducing the I/O overload by using a contiguous memory chunk.

    • Improving the vectorized tuples' column reader/writer performance.

Breaking changes

  • Removed a deprecated property, siren.io.netty.maxDirectMemory, in favor of the siren.memory.root.limit setting.

  • If Search Guard is the configured security system, the node-level setting searchguard.allow_custom_headers: "siren.*" must be added to each node of the cluster.

  • Changed the format of the JSON response for Cluster APIs Nodes Statistics .

Bug fixes

  • Fixed a join cache issue with Elastic Stack Security’s templated queries when they include a placeholder such as {{ _user: user.name }}.

  • Fixed a ConcurrentModificationException in the select phase following a recent change in Elasticsearch version 7.15 involving the FieldUsageTrackingDirectoryReader.

  • Adjusted the validation query in the datasource validation endpoint with the latest Avatica JDBC connector.

  • Adjusted the autoCommit setting to work with the latest Avatica JDBC connector.

  • Fixed a rare issue where a cluster is unable to initialize a Federate job due to a closed RootBufferManager on a node.

  • Fixed a broken link to the _sample method in the connector APIs documentation.