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

Make inline_table_scan optimize whole plan during first optimization stage. #5364

Closed
jackwener opened this issue Feb 22, 2023 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@jackwener
Copy link
Member

jackwener commented Feb 22, 2023

Describe the bug
Due to TableScan may in the subquery. So when inline_table_scan is first rule, we can't optimize it in first optimization stage.

If first optimization stage push down projection into this scan, inline_table_scan will be useless to this scan.

such as

predicate
  subquery
    table_scan (notice this scan)
table_scan

inline_table_scan ->

predicate
  subquery
    table_scan (non-inlined)
table_scan (have inlined)

-> unnest subquery

join
  table_scan (non-inlined)
  table_scan (have inlined)

notice: if pushdown projection into table_scan (non-inlined)
this scan will can't be inlined.

To Reproduce

#5366 now fail in this problem.

Expected behavior

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant