Skip to content

Add release notes for v8.18.0 release #126735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 15, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
revert highlights to edited version
  • Loading branch information
leemthompo authored Apr 15, 2025
commit 02c239b72a8a6ab8f9c2d5712079d15eef7522d0
29 changes: 13 additions & 16 deletions docs/reference/release-notes/highlights.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -36,33 +36,30 @@ endif::[]

[discrete]
[[add_new_experimental_rank_vectors_mapping_for_late_interaction_second_order_ranking]]
=== Add new experimental `rank_vectors` mapping for late-interaction second order ranking
Late-interaction models are powerful rerankers. While their size and overall cost doesn't lend itself for HNSW indexing, utilizing them as second order reranking can provide excellent boosts in relevance. The new `rank_vectors` mapping allows for rescoring over new and novel multi-vector late-interaction models like ColBERT or ColPali.
=== `rank_vectors` field type is now available for late-interaction ranking

{es-pull}118804[#118804]
<<rank-vectors,`rank_vectors`>> is a new field type released as an experimental feature in {es} {minor-version}. It is designed to be used with dense vectors and allows for late-interaction second order ranking.

Late-interaction models are powerful rerankers. While their size and overall cost doesn't lend itself for HNSW indexing, utilizing them as second order reranking can provide excellent boosts in relevance. The new `rank_vectors` mapping allows for rescoring over new and novel multi-vector late-interaction models like ColBERT or ColPali.

[discrete]
[[enable_lookup_join_in_non_snapshot_builds]]
=== Enable LOOKUP JOIN in non-snapshot builds
This effectively releases LOOKUP JOIN into tech preview. Docs will
follow in a separate PR.

- Enable the lexing/grammar for LOOKUP JOIN in non-snapshot builds.
- Remove the grammar for the unsupported `| JOIN ...` command (without `LOOKUP` as first keyword). The way the lexer modes work, otherwise we'd also have to enable `| JOIN ...` syntax on non-snapshot builds and would have to add additional validation to provide appropriate error messages.
- Remove grammar for `LOOKUP JOIN index AS ...` because qualifiers are not yet supported. Otherwise we'd have to put in additional validation as well to prevent such queries.
=== {esql} LOOKUP JOIN is now available in technical preview

Also fix https://github.com/elastic/elasticsearch/issues/121185
<<esql-lookup-join,LOOKUP JOIN>> is now available in technical preview.
LOOKUP JOIN combines data from your {esql} queries with matching records from a lookup index, enabling you to:

{es-pull}121193[#121193]
* Enrich your search results with reference data
* Speed up root-cause analysis and security investigations
* Join data across indices without complex queries
* Reduce operational overhead when correlating events

[discrete]
[[release_semantic_text_as_ga_feature]]
=== Release semantic_text as a GA feature
semantic_text is now an official GA (generally available) feature! This field type allows you to easily set up and perform semantic search with minimal ramp up time.
=== The `semantic_text` field type is now GA

{es-pull}124670[#124670]
<<semantic-text,`semantic_text`>> is now an official GA (generally available) feature! This field type allows you to easily set up and perform semantic search with minimal ramp up time.

// end::notable-highlights[]

// end::notable-highlights[]