-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[ML] Adding internal input types #132849
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
[ML] Adding internal input types #132849
Conversation
Pinging @elastic/ml-core (Team:ML) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The INTERNAL enums are very trappy. The reason they exist is to allow ingest and search operations in Elasticsearch that use the inference API to specify the intended use without having to know if the service supports the distinction between ingest and search.
Some services do not distinguish between ingest and search and we don't want them throwing a validation error saying I don't do search/ingest embeddings.
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 1f9b6bb)
(cherry picked from commit 1f9b6bb)
This PR adds the
internal
InputType
values to the translation logic for EIS.I'm backporting this because the internal values were added in 8.19 and 9.1 from this PR: #122638