Julian Hyde commented on CALCITE-1389:

I'm happy for these changes to go in. But I'd like to have a sense for where 
the effort is going - and where it fits with related efforts.

How would you feel about creating a page in our documentation about 
materialized views? It would cover regular materializations (with their 
general-purpose matching algorithm), lattices (specialized for SPJA), planning 
secondary indexes (as [~maryannxue] has done in Phoenix), view recommendations, 
and life cycle issues (how do we invalidate materialized views? how to add the 
necessary hooks so that they appear in the schema). We could discuss which 
query patterns each kind of MV can handle; and compare with MVs in other 
systems such as Cassandra and Druid; and list some of the possible future 
directions. It would help our users figure out which are the best pieces of our 
(complicated) framework to use.

> Add rule to perform rewriting of queries using materialized views with joins
> ----------------------------------------------------------------------------
>                 Key: CALCITE-1389
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1389
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Mior
>            Assignee: Michael Mior
>             Fix For: 1.11.0
>  I've been looking into implementing the approach from the following paper. 
> It's very nicely written and easy to follow. It also doesn't require trying 
> different join permutations. I'm starting with several additional 
> restrictions (only equijoins, no aggregations, etc.)
> ftp://ftp.cse.buffalo.edu/users/azhang/disc/SIGMOD/pdf-files/331/202-optimizing.pdf
> Thanks to [~jcamachorodriguez] for his help in sorting out some issues with 
> the rule so far.

This message was sent by Atlassian JIRA

Reply via email to