fix(cubesql): Break cost symmetry for (non)-push-to-Cube WrappedSelect #9155
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.
Check List
Description of Changes Made (if issue reference is not provided)
Break symmetry for pust-to-Cube vs non-push-to-Cube plans, and test pushed members count on simple query.
Consider this query:
It can be represented with these two wrapper plans:
Without changes in cost both of those would have the same cost:
Which one of those will get executed is implementation defined, and right now top-down and bottom-up cost choose different plans.