[
https://issues.apache.org/jira/browse/CALCITE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941893#comment-17941893
]
Zhen Chen commented on CALCITE-6925:
------------------------------------
Hi, [~julianhyde] Thank you very much for initiating this discussion. In my
view, the entire execution process of Calcite involves two layers plan. The
first stage generates a "logical" plan, the second stage produces an Enumerable
or Jdbc or other plan (which can be temporarily called as the "physical" plan).
The first-stage plan should operate at the relational algebra level and is
typically used for plan rewriting. The second-stage plan contains physical
properties. While it wouldn't be problematic for both stages to consider
physical properties, it might introduce unnecessary complexity and redundancy.
Therefore, not considering physical properties in the first-stage plan (the
so-called "logical" plan) would make the roles of the two planning stages
clearer. Currently, the "logical" operators have implemented the "sort" trait,
which can remain unchanged. However, not all operators have implemented the
"distribution" trait, and there are no test cases covering it. Perhaps we could
remove the "distribution" trait.
I don't know if my understanding is wrong, if so please correct me.
> Logical operator should remove RelDistributionTraitDef
> ------------------------------------------------------
>
> Key: CALCITE-6925
> URL: https://issues.apache.org/jira/browse/CALCITE-6925
> Project: Calcite
> Issue Type: Bug
> Reporter: Zhen Chen
> Assignee: Zhen Chen
> Priority: Major
> Labels: pull-request-available
>
> Some logical operator (such as LogicalFilter) contains distribution trait,
> this trait is a physical trait. we maybe can remove it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
