frontend: Fix downstream queries in experimental subquery spin-off feature #10603
Conversation
This file contains 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
…ature Massive oversight in #10460. The downstream queries were all just `__query__` instead of the actual query. I also optimized the mapper so that it groups downstream queries further up the tree, which should reduce the number of queries that need to be run.
aknuds1
reviewed
Feb 7, 2025
aknuds1
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Massive oversight in #10460
The downstream queries were all just
__query__instead of the actual query. I also optimized the mapper so that it groups downstream queries further up the tree, which should reduce the number of queries that need to be run.Most queries when testing were still passing since joining subqueries and non subqueries is pretty rare in practice, it seems