We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
TableScan
subquery
inline_table_scan
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.
table_scan (non-inlined)
To Reproduce
#5366 now fail in this problem.
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered:
subquery-unnest
Unnest
Successfully merging a pull request may close this issue.
Describe the bug
Due to
TableScan
may in thesubquery
. So wheninline_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
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
The text was updated successfully, but these errors were encountered: