Hi colleagues,
I would like to discuss with the community the possibility of adding a new
public method to VolcanoPlanner which will forcefully re-trigger the rules
for the specific rel. This is a follow up of a discussion started in the
other thread [1].
**Problem statement**
When converting bet
Not only "fireRule" method is needed, but the way to get all parents of a
set, containing a subset, produced by the transformation. Or a way to fire
rules without traits satisfaction check.
чт, 31 окт. 2019 г., 10:56 Vladimir Ozerov :
> Hi colleagues,
>
> I would like to discuss with the communit
Yunpeng Niu created CALCITE-3463:
Summary: Parse SQL Query - Non-query expression encountered in
illegal context
Key: CALCITE-3463
URL: https://issues.apache.org/jira/browse/CALCITE-3463
Project: Calc
Thanks Vladimir for bringing up this discussion !
Did you notice that there is a JIRA issue about this problem ? [1] Also a
discussion about how to propagate the traits [2]
[1] https://issues.apache.org/jira/browse/CALCITE-2970
[2]
https://ponymail-vm.apache.org/_GUI_/thread.html/79dac47ea50b5d
Wang Yanlin created CALCITE-3464:
Summary: RexSimplify simplifies plan having filter with NULL to
empty values
Key: CALCITE-3464
URL: https://issues.apache.org/jira/browse/CALCITE-3464
Project: Calcit
Alessandro Solimando created CALCITE-3465:
-
Summary: Cover Cassandra 3.x data types
Key: CALCITE-3465
URL: https://issues.apache.org/jira/browse/CALCITE-3465
Project: Calcite
Issue Ty
Hello,
I have logged a Jira ticket for this:
https://issues.apache.org/jira/browse/CALCITE-3465
I have listed all the data types for Cassandra 3.x, and I have tried to
compile a table with the current status, but there are few entries for
which I am not sure.
If you have time to contribute to the
Hi Danny,
Thank you very much for the links. What is described here is pretty much
similar to the problem I describe. Especially the discussion about trait
propagation, as this is basically what I need - to explore potential traits
of children before optimizing parents. And this is basically what
Wang Weidong created CALCITE-3466:
-
Summary: JDBC adapter dropped group by statement in subquery
Key: CALCITE-3466
URL: https://issues.apache.org/jira/browse/CALCITE-3466
Project: Calcite
Iss
xzh_dz created CALCITE-3467:
---
Summary: fix PartialMapping mistake and Cosmetic Change
Key: CALCITE-3467
URL: https://issues.apache.org/jira/browse/CALCITE-3467
Project: Calcite
Issue Type: Wish
Hi Vladimir,
I think for short/mid term, #2 way (using AbstractConverter) should work after
we fix CALCITE-2970. We already understand the root cause, now are looking at
the best way to fix it. If you cannot wait, you can also create your own
converter rule so it won’t generate logical node, an
Hi Xiening,
Yes, I think that the manual creation of converters to trigger parent rules
should be enough at the moment. I'll try to explore this possibility. Thank
you.
Regards,
Vladimir
чт, 31 окт. 2019 г. в 20:11, Xiening Dai :
> Hi Vladimir,
>
> I think for short/mid term, #2 way (using Abst
Hi Vladimir,
The SubsetTransformer interface and the iterating over the RelNodes
within a RelSubset in Drill is exactly implemented to do the trait
propagation. We also had to rely on AbstractConverter to fire
necessary rule to avoid the CanNotPlan issue. At some point, Calcite
community chooses
Lindsey Meyer created CALCITE-3468:
--
Summary: Oracle cast to varchar does not use precision when it
should
Key: CALCITE-3468
URL: https://issues.apache.org/jira/browse/CALCITE-3468
Project: Calcite
Actually we solved this problem in our setup using a mechanism called “Pull-Up
Traits”, which explores the possible trait set of children’s input to decide
parent’s physical properties. In order to determine child input trait, you
would have to look at child’s children, and all the way to the le
Hi Xiening,
"Let say if R and S doesn’t have sorting properties at all. In your
case, we would end up adding enforcers for LHS and RHS to get
collation (a, b, c). Then we would need another enforcer to get
collation (b, c). This is a sub optimal plan as we could have use (b,
c, a) for join."
In s
I think "pull-up traits" is necessary, since the physical traits are
propagated upwards. However, I'm not fully convinced "On Demand
Trait" is the best solution, as I feel it may restrict the choices the
planner may consider. Maybe after the proposed design doc is ready,
we may look into the deta
17 matches
Mail list logo