You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Justin Swett (Jira)" <ji...@apache.org> on 2020/09/24 16:06:00 UTC

[jira] [Created] (CALCITE-4276) Rewriting for materialized view will project wrong input

Justin Swett created CALCITE-4276:
-------------------------------------

             Summary: Rewriting for materialized view will project wrong input
                 Key: CALCITE-4276
                 URL: https://issues.apache.org/jira/browse/CALCITE-4276
             Project: Calcite
          Issue Type: Bug
          Components: core
            Reporter: Justin Swett
         Attachments: TemporalMaterializationWithJoinsTest.java

When MaterializedViewOnlyAggregateRule does its rewrite it will sometimes produce a project above the materialized view that references the incorrect input. For example,

Materialization Rel:
{noformat}
LogicalAggregate(group=[{0}], ORDER_ITEMS.ORDER_SIZE=[COUNT()], ORDER_ITEMS.ORDER_SUM=[$SUM0($1)])
  LogicalProject(ORDER_ID=[$1], AMOUNT=[$2])
    2(table=[[orders_items]]){noformat}
Query Rel:
{noformat}
LogicalAggregate(group=[{0}], agg#0=[COUNT()])
  LogicalProject($f0=[FLOOR($1, FLAG(YEAR))])
    LogicalJoin(condition=[=($0, $1)], joinType=[inner])
      LogicalProject(ORDER_ID=[$1])
        2(table=[[orders_items]])
      LogicalProject(ID=[$0], CREATED_AT=[$4])
        4(table=[[orders]]){noformat}
Will Produce the following rel after MaterializedViewOnlyAggregateRule fires:
{noformat}
LogicalAggregate(group=[{8}], agg#0=[$SUM0($1)])
  LogicalProject(ORDER_ID=[$0], ORDER_ITEMS.ORDER_SIZE=[$1], ORDER_ITEMS.ORDER_SUM=[$2], ID=[$3], USER_ID=[$4], ORDER_AMOUNT=[$5], STATUS=[$6], CREATED_AT=[$7], $f8=[FLOOR($0, FLAG(YEAR))])
    LogicalFilter(condition=[=($0, $3)])
      LogicalJoin(condition=[true], joinType=[inner])
        6(table=[[testing_mv]])
        4(table=[[orders]]){noformat}
Notice the "*$f8=[FLOOR($0, FLAG(YEAR))*" the $0 is pointing to the test_mv order_id field, so perhaps something with the filter?

The attached test case reproduces the issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)