fix(elasticsearch): fix filtering on nested fields #5643
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the following changes to support filtering on paths like
foo.bar.baz
:foo
is an object,isNestedField()
now returnstrue
instead offalse
foo
is an object,getNestedFieldPath()
now returns"foo.bar"
instead ofnull
foo
is a collection,getNestedFieldPath()
now returns"foo.bar"
instead of just"foo"
(matching the behavior iffoo
is an object)As a result, filtering on deeply-nested paths (with 3 or more levels) now produces the following query: