You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (Jira)" <ji...@apache.org> on 2020/02/26 05:02:00 UTC

[jira] [Created] (CALCITE-3825) Split AbstractMaterializedViewRule into multiple classes

Jesus Camacho Rodriguez created CALCITE-3825:
------------------------------------------------

             Summary: Split AbstractMaterializedViewRule into multiple classes
                 Key: CALCITE-3825
                 URL: https://issues.apache.org/jira/browse/CALCITE-3825
             Project: Calcite
          Issue Type: Improvement
          Components: core
            Reporter: Jesus Camacho Rodriguez
            Assignee: Jesus Camacho Rodriguez


AbstractMaterializedViewRule contains a materialized view-based rewriting algorithm that has been there for multiple releases and it is used by some engines relying in Calcite, e.g., Apache Hive.
The main reason to have a single file/class for the rule was to make the logic self-contained instead of spreading it between multiple files from the onset, as it was experimental and we were not sure how far the implementation would go. In retrospective, we should have refactor that code sooner rather than later, since it makes very difficult to understand and maintain logic that is already complicated enough.

This issue is to split AbstractMaterializedViewRule into multiple files/classes (it already contained multiple internal classes).



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