[ML][Transform] Use field_caps API for mapping deduction #46703
Merged
Conversation
This file contains 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
|
Pinging @elastic/ml-core |
|
@elasticmachine update branch |
|
run elasticsearch-ci/docs |
benwtrent
deleted the
feature/ml-transform-use-field-caps-for-type-deduction
branch
This was referenced Sep 16, 2019
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Sep 16, 2019
benwtrent
added a commit
that referenced
this pull request
Sep 16, 2019
benwtrent
added a commit
that referenced
this pull request
Oct 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Getting the mapping directly causes some problems, and is more complicated than just using the field caps API.
This updates
SchemaUtilto use the field caps API instead of getting the raw mapping of the source indices.closes #46694