fix(sql): constant in explicit group by should not remove parallel optimisation #4384
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.
Closes #4380
This is related to Clickbench Q34. Adding an explicit group by that includes an effectively constant expression would prevent generation of Async Group By node.
Change also sorted the ordering of the SqlOptimiser tests. This makes locating the relevant test hard. It is here:
questdb/core/src/test/java/io/questdb/test/griffin/SqlOptimiserTest.java
Lines 194 to 235 in b74fb84
Control query:
Gives:
Problematic query:
Plan before:
Plan after: