-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Misbehaviour when using missing filter on fields which have the same name as _type #7962
Comments
Hi @mcuelenaere Thanks for reporting this. A simpler recreation follows:
This explain:
Returns:
While this explain:
Incorrectly returns:
|
For reference this is an old bug, I could reproduce it with 1.1 and it probably also reproduces on earlier versions. Since we don't index anything for inner nodes of a json object, when we get an exists/missing filter on a field So in the end we try to match on |
I'm closing in favor of #4081, the issue here is that elasticsearch tried to interpret the first part of the field name as a type. |
When using the missing filter on a field which has the same name as _type, it seems to get transformed to a match_all filter:
The text was updated successfully, but these errors were encountered: