[
https://issues.apache.org/jira/browse/CALCITE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413683#comment-17413683
]
Alessandro Solimando commented on CALCITE-4770:
-----------------------------------------------
If I am not wrong, the current MV matching system in Calcite is based on
"[Optimizing queries using materialized views: a practical, scalable
solution|https://dl.acm.org/doi/10.1145/375663.375706]";.
It seems there are some overlapping with what you propose, and they already
have some sophisticated data structure to speed up the testing of some
conditions (e.g., checking that all the needed columns for the SQL query are
available in the MV by using equivalence classes of columns to avoid false
negatives).
It would be useful to compare with what they propose (and check what is
actually implemented in Calcite, which can just be a subset of what's in the
paper).
> Design of SearchMvService
> -------------------------
>
> Key: CALCITE-4770
> URL: https://issues.apache.org/jira/browse/CALCITE-4770
> Project: Calcite
> Issue Type: New Feature
> Reporter: xzh_dz
> Priority: Major
>
> In the data system, materialized view can speed up SQL query. Materialized
> view represents the pre-calculated SQL logic of the target table and contains
> real data. In the project, we use materialized views to speed up SQL queries,
> use the materialized view recognition technology to identify materialized
> views, and enhance the ability of materialized recognition. However, with
> more and more materialized views , materialized view recognition takes a lot
> of time, which seriously affects the performance of SQL queries. With this
> problem, we propose a design of accurate search materialized view based on
> operator features.
> DOC：[Design of
> SearchMvService|[https://docs.google.com/document/d/1mmAsK_uW-fBs893JERP1gspMurX2lNXcVGeesP4XUqQ/edit]]
> Welcome to discuss and expect more feedback,thank you.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
