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
Propagate percolate mapping changes to cluster state #5776
Propagate percolate mapping changes to cluster state #5776
Conversation
…ping service, then those changes should be updated in cluster state of the master as well.
LGTM, +1 on later brining the duplicate code into the same place. |
LGTM +1 to push |
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well. Closes #5776
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well. Closes #5776
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well. Closes #5776
@martijnvg I pushed this to all relevant branches |
Thanks Simon! On 15 April 2014 19:35, Simon Willnauer notifications@github.com wrote:
Met vriendelijke groet, Martijn van Groningen |
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well. Closes elastic#5776
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well. Closes elastic#5776
If the during percolating a new field was introduced in the local mapping service, then those changes should be updated in cluster state of the master as well.