Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Transform] create explicit object mappings for nested field #51321

Closed
hendrikmuhs opened this issue Jan 22, 2020 · 1 comment · Fixed by #51368
Closed

[Transform] create explicit object mappings for nested field #51321

hendrikmuhs opened this issue Jan 22, 2020 · 1 comment · Fixed by #51368
Labels
>enhancement :ml/Transform Transform

Comments

@hendrikmuhs
Copy link
Contributor

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 for a.b.c only. This opens up a corner case:

  • a conflicting index template could exists for a or a.b (as reported by a user)

(Note that a conflicting mapping in the config is already handled in validation)

Solution:

  • introduce explicit object mappings for nested fields
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

hendrikmuhs pushed a commit to hendrikmuhs/elasticsearch that referenced this issue Jan 23, 2020
insert explict mappings for objects in nested output to avoid clashes…
54ecb1f 
… with

index templates

fixes elastic#51321
@hendrikmuhs hendrikmuhs mentioned this issue Jan 23, 2020
Merged
hendrikmuhs pushed a commit to hendrikmuhs/elasticsearch that referenced this issue Jan 27, 2020
insert explict mappings for objects in nested output to avoid clashes…
af3ac6e 
… with

index templates

fixes elastic#51321
hendrikmuhs pushed a commit that referenced this issue Jan 28, 2020
[Transform] avoid mapping problems with index templates (#51368)
4d11e1a 
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
[Transform] avoid mapping problems with index templates (elastic#51368)
87cc8e5 
insert explict mappings for objects in nested output to avoid clashes with index templates

fixes elastic#51321
@hendrikmuhs hendrikmuhs mentioned this issue Jan 28, 2020
Merged
hendrikmuhs pushed a commit that referenced this issue Jan 28, 2020
[Transform] avoid mapping problems with index templates (#51368) (#51519
2239ba8 
)

insert explict mappings for objects in nested output to avoid clashes with index templates

fixes #51321
@codebrain codebrain mentioned this issue Apr 1, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement :ml/Transform Transform
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Transform] avoid mapping problems with index templates hendrikmuhs/elasticsearch
2 participants
@hendrikmuhs @elasticmachine