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.

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

Mappings: dynamic mapping updates should use the same path as mapping updates from the API #9364

Closed
jpountz opened this issue Jan 20, 2015 · 1 comment · Fixed by #10593
Closed
Assignees
Labels
>enhancement help wanted adoptme :Search/Mapping Index mappings, including merging and defining field types v2.0.0-beta1

Comments

@jpountz
Copy link
Contributor

jpountz commented Jan 20, 2015

Currently we have two different code paths for dynamic mapping updates and mapping updates that come from the API.

I think we should improve it by making document parsing generate mapping updates, and then apply these mapping updates just like we apply mapping updates that come from the API.

This would probably help with #8688

@jpountz jpountz added v2.0.0-beta1 :Search/Mapping Index mappings, including merging and defining field types labels Jan 20, 2015
@rjernst rjernst self-assigned this Jan 20, 2015
@jpountz
Copy link
Contributor Author

jpountz commented Jun 3, 2015

Closed via #10593

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement help wanted adoptme :Search/Mapping Index mappings, including merging and defining field types v2.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants