Also regarding that Projects merging is common in Calcite optimization
rules, we should always remember to avoid merging for cases like the one
given by Rommel.
I think that would be hard.
Best,
Jin
XING JIN 于2019年10月14日周一 上午11:51写道：
> Hi, Stamatis, Danny~
>
> Thanks for explain ~
>
> > "The
Hi, Stamatis, Danny~
Thanks for explain ~
> "The consumer in the case of P1 is the project which only needs $0, $2,
$5,
$6 so the trimmer could slim down the scan by projecting only these fields."
I think RelFieldTrimmer is already doing this by [1].
But why the final BindableTableScan is not
liuzonghao created CALCITE-3406:
---
Summary: duplicate initialize scope
Key: CALCITE-3406
URL: https://issues.apache.org/jira/browse/CALCITE-3406
Project: Calcite
Issue Type: Improvement
+1, RelFieldTrimmer is the role to trim the unused fields.
Best,
Danny Chan
在 2019年10月13日 +0800 AM6:25，dev@calcite.apache.org，写道：
>
> RelFieldTrimmer
OK，I got your point.
Thanks for sharing.
| |
王炎林
|
|
邮箱：1989yanlinw...@163.com
|
签名由 网易邮箱大师 定制
On 10/13/2019 06:17, Stamatis Zampetakis wrote:
I was thinking that RelFieldTrimmer can be used to transform the plan P1 to
plan P2 and then ProjectTableScanRule can be used to introduce the
