[
https://issues.apache.org/jira/browse/CALCITE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413995#comment-17413995
]
Alessandro Solimando commented on CALCITE-4770:
-----------------------------------------------
Hi [~wojustme], I am not saying that the paper is used (or should be used)
everywhere in Calcite, I am rather suggesting a comparison of the data
structures and associated "compatibility checks" from the paper and those from
your proposal.
I see some overlapping between the paper and the proposal (they are both trying
to reduce the number of MVs), so I think that understanding how your proposal
extends the paper could be beneficial for both *MaterializedViewRule#perform*
and ** *SubstitutionVisitor#go*.**
> 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)
