Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cubesql): Initial SQL pushdown flattening #8888

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

mcheshkov
Copy link
Member

Check List

  • Tests has been run in packages where changes made if available
  • Linter has been run for changed code
  • Tests for the changes have been added if not covered yet
  • Docs have been added / updated if required

Description of Changes Made (if issue reference is not provided)

[Description goes here]

This case is already covered with compile::test::test_wrapper::test_wrapper_limit_zero
…h_to_cube

This name seems more appropriate, because actual WrappedSelect can represent grouped query when this field is set to true
…up replacers

It is used to track whether this query actually wraps ungrouped scan in from as opposed to old flag, which is used as push to cube enabler
…out push to Cube

* New wrapped_no_push_to_cube cost component, necessary when two wrappers does not differ at all, only by push_to_cube flag
…uped=true)) with enabled push to Cube

This is necessary to build proper representations for flattening
Some queries in tests reduced to a single CubeScan with member expressions, so tests have changed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant