Sorry for the late response, I lost track of this email.
Anupam> I don't think HepPlanner does MV substitution (add materialization
method
on the RelOptPlanner is not overloaded in HepPlanner)
You would have to use VolcanoPlanner and instantiate with the same rules
you did for HepPlanner.
Hello Devs!
You're receiving this email because you are subscribed to one or more
Apache developer email lists.
I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago. It will be held May 13th and 14th at
three bars in the Logan Square
Thank you Julian and Stamatis for the clarification. While debugging I
observed that in MultiJoin operator there were only two tables
participating in the join ordering for the below query.
Here is the query which I could see a difference in the plan (in Drill).
0: jdbc:drill:zk=local> alter
Hongze Zhang created CALCITE-2787:
-
Summary: Json aggregate calls with different null clause get
incorrectly merged during converting from sql to rel
Key: CALCITE-2787
URL:
Hongze Zhang created CALCITE-2786:
-
Summary: Add order by clause support for JSON_ARRAYAGG
Key: CALCITE-2786
URL: https://issues.apache.org/jira/browse/CALCITE-2786
Project: Calcite
Issue
Hongze Zhang created CALCITE-2785:
-
Summary: In EnumerableAggregate, wrong result produced If there
are sorted aggregates and non-sorted aggregates at the same time.
Key: CALCITE-2785
URL:
Hi all,
Recently, I am studying the code about how Calcite deals with
ExpandSelectStar. I get a rough picture of it, but there is some confusion
about the Dynamic Table which gets a special deal when expanding SelectStar.
I wonder what is the Dynamic Table, which cases it deals with and why it
