fix issue with nested virtual column index supplier for partial paths when processing from raw #15643
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.
Description
Fixes an issue when filtering
NestedFieldVirtualColumn
using 'processFromRaw' (e.g.JSON_QUERY
instead ofJSON_VALUE
) when using partial paths.NestedFieldVirtualColumn
was incorrectly returningnull
fromgetIndexSupplier
in this case instead ofNoIndexesColumnIndexSupplier.getInstance()
to instruct the processing to fall back to using value matchers. Added test case for this, as well as another similar case which was working correctly where it should also fall back to using no-indexes when referring to an array element, to ensure no future regressions.This PR has: