Make indexing work over complex JSON collections #36444
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
roji force-pushed the ComplexJsonIndexing branch from 42ed46b to f7e01ea Compare 16 tasks
cincuranet approved these changes Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
We have some technical debt around how indexing is managed in the query pipeline; see comments in the changes for more context. In this PR I did my best to make things work for complex collections in a way that's aligned with how they already work for owned entities, to keep things simple and not add more hacks. We should get back to this and re-architect/clean up at some point (#36335, #30386).
Part of #36296
/cc @artl93