-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Transform] create explicit object mappings for nested field #51321
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 23, 2020
… with index templates fixes elastic#51321
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 27, 2020
… with index templates fixes elastic#51321
hendrikmuhs
pushed a commit
that referenced
this issue
Jan 28, 2020
insert explict mappings for objects in nested output to avoid clashes with index templates fixes #51321
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 28, 2020
insert explict mappings for objects in nested output to avoid clashes with index templates fixes elastic#51321
hendrikmuhs
pushed a commit
that referenced
this issue
Jan 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When auto-creating the destination index, transform deducts appropriate mappings, however it creates the mappings only for the leafs, meaning if the field is nested like
a.b.c
it creates a mapping fora.b.c
only. This opens up a corner case:a
ora.b
(as reported by a user)(Note that a conflicting mapping in the config is already handled in validation)
Solution:
The text was updated successfully, but these errors were encountered: