-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Conversation
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
I'm running the full test suite against this now but I figured it was worth opening quickly. This doesn't make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Note that this PR is against the 5.x branch only and we'll backport all the way to the 5.2 branch. |
Thanks! |
Thanks @jasontedor! Backported! |
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 #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 #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 insteadreturn a deprecation warning.
include_in_all
in a multifieldstill doesn't do anything. But at least people who use it erroneously
won't break.
Closes #23654