--
> 发件人：Vladimir Ozerov
> 日 期：2020年03月15日 04:18:53
> 收件人：Haisheng Yuan
> 抄 送：dev@calcite.apache.org (dev@calcite.apache.org) >
> 主 题：Re: Re: Re: Re: [DISCUSS] Proposal to add API to force rules matching
> specific rel
calls.
- Haisheng
--
发件人：Vladimir Ozerov
日 期：2020年03月15日 04:18:53
收件人：Haisheng Yuan
抄 送：dev@calcite.apache.org (dev@calcite.apache.org)
主 题：Re: Re: Re: Re: [DISCUSS] Proposal to add API to force rules matching
specific rels
Hi Haisheng,
01:50:10
> 收件人：dev@calcite.apache.org (dev@calcite.apache.org) >
> 主 题：Re: Re: Re: [DISCUSS] Proposal to add API to force rules matching
> specific rels
>
> Hi Roman,
>
> In my understanding, the proposed minor changes may only decrease the total
> number of rule invoc
1:50:10
收件人：dev@calcite.apache.org (dev@calcite.apache.org)
主 题：Re: Re: Re: [DISCUSS] Proposal to add API to force rules matching specific
rels
Hi Roman,
In my understanding, the proposed minor changes may only decrease the total
number of rule invocations slightly, but all principal problems remain the
same.
Hi Roman,
In my understanding, the proposed minor changes may only decrease the total
number of rule invocations slightly, but all principal problems remain the
same. In the top-down approach, you do not want to implement bottom logical
nodes unless it is requested explicitly by a parent operator.
On the other hand, if we don't preprocess and normalize the rel expression
before going to valcano planner, still compute and keep logical/relational
properties, like cardinality, for each operator, how can we achieve group seach
space pruning? Given a physical group expression, its required pro
