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

Mapping updates on objects should propagate `include_an_all`. #20051

Merged
merged 1 commit into from Aug 18, 2016

Conversation

Projects
None yet
2 participants
@jpountz
Contributor

jpountz commented Aug 18, 2016

Today you can't update include_an_all on an existing object. The bug affects
2.x too.

@jimczi

This comment has been minimized.

Show comment
Hide comment
@jimczi

jimczi Aug 18, 2016

Member

LGTM

Member

jimczi commented Aug 18, 2016

LGTM

Mapping updates on objects should propagate `include_an_all`. #20051
Today you can't update `include_an_all` on an existing object. The bug affects
2.x too.

@jpountz jpountz merged commit 8f8ae8f into elastic:master Aug 18, 2016

1 of 2 checks passed

elasticsearch-ci Build started sha1 is merged.
Details
CLA Commit author is a member of Elasticsearch
Details

jpountz added a commit that referenced this pull request Aug 18, 2016

Mapping updates on objects should propagate `include_an_all`. #20051
Today you can't update `include_an_all` on an existing object. The bug affects
2.x too.

@jpountz jpountz deleted the jpountz:fix/carry_on_include_in_all_on_merge branch Aug 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment