We’re happy to announce today the release of Siren Federate version 35.0 for Elasticsearch 7.17.20. This release includes the following improvements, features and bug fixes:
Improvements
- Upgraded to Elasticsearch 7.17.20
- Improved the circuit-breaker mechanism for multi-conditional index joins. The circuit-breaker now triggers a failure when the limit of index lookup operations is exceeded at run-time, rather than relying on estimations done at the query planning phase.
- Enhanced the failure message of the circuit-breaker mechanism for multi-conditional index joins, incorporating details on the reached limit and the count of remaining lookup operations.
- Introduced an option to deactivate the circuit-breaker mechanism for multi-conditional index joins. This can be achieved by setting -1 in the
federate.planner.index_join.max_lookupsconfiguration setting. - Improved the error messages by removing the exception classes from the list of obfuscated classes.
- Improved the cost model to select
sorted set terms scanoverindex scanwhen we project only one column.
Features
- Added folding capabilities to AQP (Adaptive Query Planner) requests.
- Introduced a
federate_objectruntime field to construct custom objects (map-like structures) to maintain correlation between field values from the same document.
Bug fixes
- Fixed a bug concerning
missing boundsand multi-value columns. - Fixed a folding/cache bug in the multi-conditional and broadcast join that was causing a
Data entry does not existfailure. - Fixed orphan thread executions when the REST channel is closed before finishing the request.
- Fixed a
missing-indexerror for an unavailable index when explicitly theignore_unavailableparameter was set totrue. - Fixed a performance regression issue caused by a
fieldExistsquery for a runtime field used in a join.
Download it here .