-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[ML] Do not create inference endpoint if ID is used in existing mappings #137055
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
DonalEvans
merged 9 commits into
elastic:main
from
DonalEvans:check-existing-semantic-text-fields-when-creating-inference-endpoint
Nov 3, 2025
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
9d5ca1c
Do not create inference endpoint if ID is used in existing mappings
DonalEvans 98a0091
Update docs/changelog/137055.yaml
DonalEvans 5fb900e
Reword error message
DonalEvans 614a61e
Merge branch 'main' into check-existing-semantic-text-fields-when-cre…
DonalEvans e95e06e
Fix failing test
DonalEvans a6fba17
Check model settings for existing semantic text fields
DonalEvans 5ec69c7
Merge branch 'main' into check-existing-semantic-text-fields-when-cre…
DonalEvans d566301
Restore default visibility to MinimalServiceSettings constants
DonalEvans d33ebfb
Merge branch 'main' into check-existing-semantic-text-fields-when-cre…
DonalEvans File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| pr: 137055 | ||
| summary: Do not create inference endpoint if ID is used in existing mappings | ||
| area: Machine Learning | ||
| type: bug | ||
| issues: | ||
| - 124272 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
46 changes: 0 additions & 46 deletions
46
...n/core/src/main/java/org/elasticsearch/xpack/core/ml/utils/SemanticTextInfoExtractor.java
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Seems like this should fail even if there aren't any docs in the index.
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.
Do you mean that it should fail if no docs with semantic text fields were ever indexed, or it should fail if docs were indexed but then removed from the index? In the former case, we wouldn't have stored the model details, because that information is only populated when we get the inference results back when ingesting a document with a semantic text field. In the latter case, the endpoint creation does fail with these changes, because the semantic text field mapping isn't cleared when documents are deleted.
Since we don't persist information about the model until a doc with a semantic text field is indexed, I don't think there's any risk to the user if they create an endpoint with certain settings, delete it, then create a new one with different settings, but never index any documents with semantic text fields before creating the endpoint for the second time.
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.
Yep, you are correct. I have been out of the loop here for a bit. LGTM!