Skip to content

Conversation

davidkyle
Copy link
Member

The X-elastic-product-use-case is change to be a multi-value header and the request origin (search, ingest, unspecified) added to the header for sparse and dense embedding requests. Clients can also set X-elastic-product-use-case which is why it must be a multi-value header.

The 3 potential values are

X-Elastic-Product-Use-Case: internal_search
X-Elastic-Product-Use-Case: internal_ingest
X-Elastic-Product-Use-Case: unspecified

unspecified requests come directly from the REST API

Non issue as it relates to internal comms between Elasticsearch and the Elastic Inference Service

@davidkyle davidkyle added >non-issue :ml Machine learning cloud-deploy Publish cloud docker image for Cloud-First-Testing v9.2.0 labels Sep 26, 2025
@elasticsearchmachine elasticsearchmachine added the Team:ML Meta label for the ML team label Sep 26, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

@davidkyle davidkyle enabled auto-merge (squash) September 29, 2025 09:24
@davidkyle
Copy link
Member Author

run elasticsearch-ci/part-3

@davidkyle davidkyle merged commit bc09ab3 into elastic:main Sep 30, 2025
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud-deploy Publish cloud docker image for Cloud-First-Testing :ml Machine learning >non-issue Team:ML Meta label for the ML team v9.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants