Release notes



  • Upgraded to Elasticsearch 8.13.4.

  • Enhanced Elasticsearch aggregations to work with Federate joins.

  • Improved function_score to accept join in the filters scope.

Bug fixes

  • Fixed join query failures caused by unsupported matches API used by highlighters.



  • Upgraded to Elasticsearch 8.13.2

  • 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_lookups configuration 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 scan over index scan when we project only one column.


  • Added folding capabilities to AQP (Adaptive Query Planner) requests.

  • Introduced a federate_object runtime 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 bounds and multi-value columns.

  • Fixed a folding/cache bug in the multi-conditional and broadcast join that was causing a Data entry does not exist failure.

  • Fixed orphan thread executions when the REST channel is closed before finishing the request.

  • Fixed a missing-index error for an unavailable index when explicitly the ignore_unavailable parameter was set to true.

  • Fixed a performance regression issue caused by a fieldExists query for a runtime field used in a join.