Skip to content

Allow semantic_text fields to use optional GPU indexing for HNSW and int8_hnsw#138999

Merged
elasticsearchmachine merged 3 commits intoelastic:mainfrom
benwtrent:semantic-text/pipe-through-extra-fmt-providers
Dec 3, 2025
Merged

Allow semantic_text fields to use optional GPU indexing for HNSW and int8_hnsw#138999
elasticsearchmachine merged 3 commits intoelastic:mainfrom
benwtrent:semantic-text/pipe-through-extra-fmt-providers

Conversation

@benwtrent
Copy link
Member

This pipes the extra vector format provider to semantic_text fields. This unlocks using the new experimental GPU indexing for semantic text fields.

Generally, this is also required for future work utilizing these extension format providers.

@benwtrent benwtrent added >enhancement :SearchOrg/Relevance Label for the Search (solution/org) Relevance team v9.3.0 labels Dec 3, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Search - Relevance The Search organization Search Relevance team label Dec 3, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-relevance (Team:Search - Relevance)

@elasticsearchmachine
Copy link
Collaborator

Hi @benwtrent, I've created a changelog YAML for you.

Copy link
Contributor

@Mikep86 Mikep86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM pending green CI

@@ -0,0 +1,5 @@
pr: 138999
summary: Allow `semantic_text` fields to use optional GPU indexing for HNSW and int8_hnsw
area: Relevance
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Use Vector Search instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that what we use for semantic_text? if so, I can change it :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, the Relevance area is so broad that I barely use it. Most semantic text/search changes use Vector Search, and given that this is directly related to vector formats, it seems like the best fit.

@benwtrent benwtrent added :Search Relevance/Vectors Vector search and removed :SearchOrg/Relevance Label for the Search (solution/org) Relevance team labels Dec 3, 2025
@elasticsearchmachine elasticsearchmachine added Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch and removed Team:Search - Relevance The Search organization Search Relevance team labels Dec 3, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@benwtrent benwtrent added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Dec 3, 2025
@elasticsearchmachine elasticsearchmachine merged commit 9c89d39 into elastic:main Dec 3, 2025
35 checks passed
@benwtrent benwtrent deleted the semantic-text/pipe-through-extra-fmt-providers branch December 3, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >enhancement :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v9.3.0

3 participants