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

Switch include_in_all in multifield to warning #23656

Merged
merged 1 commit into from
Mar 20, 2017

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Mar 20, 2017

This reverts #21971 which should only have been applied in master
to preserve backwards compatibility. Instead of throwing an error
when you specify include_in_all inside a multifield we instead
return a deprecation warning. include_in_all in a multifield
still doesn't do anything. But at least people who use it erroneously
won't break.

Closes #23654

This reverts elastic#21971 which should only have been applied in master
to preserve backwards compatibility. Instead of throwing an error
when you specify `include_in_all` inside a multifield we instead
return a deprecation warning. `include_in_all` in a multifield
still doesn't do anything. But at least people who use it erroneously
won't break.

Closes elastic#23654
@nik9000 nik9000 added :Search/Mapping Index mappings, including merging and defining field types blocker >bug v5.2.3 v5.3.0 v5.4.0 v6.0.0-alpha1 labels Mar 20, 2017
@nik9000
Copy link
Member Author

nik9000 commented Mar 20, 2017

I'm running the full test suite against this now but I figured it was worth opening quickly.

This doesn't make include_in_all inside of multifields work. It just removes the exception telling you it won't and replaces it with a deprecation message. We will keep the exception in 6.0.

Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@nik9000
Copy link
Member Author

nik9000 commented Mar 20, 2017

Note that this PR is against the 5.x branch only and we'll backport all the way to the 5.2 branch.

@nik9000
Copy link
Member Author

nik9000 commented Mar 20, 2017

LGTM.

Thanks!

@nik9000 nik9000 merged commit 0af590d into elastic:5.x Mar 20, 2017
@nik9000
Copy link
Member Author

nik9000 commented Mar 20, 2017

Thanks @jasontedor!

Backported!

nik9000 added a commit that referenced this pull request Mar 20, 2017
This reverts #21971 which should only have been applied in master
to preserve backwards compatibility. Instead of throwing an error
when you specify `include_in_all` inside a multifield we instead
return a deprecation warning. `include_in_all` in a multifield
still doesn't do anything. But at least people who use it erroneously
won't break.

Closes #23654
nik9000 added a commit that referenced this pull request Mar 20, 2017
This reverts #21971 which should only have been applied in master
to preserve backwards compatibility. Instead of throwing an error
when you specify `include_in_all` inside a multifield we instead
return a deprecation warning. `include_in_all` in a multifield
still doesn't do anything. But at least people who use it erroneously
won't break.

Closes #23654
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker >bug :Search/Mapping Index mappings, including merging and defining field types v5.2.3 v5.3.0 v5.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants