[
https://issues.apache.org/jira/browse/CALCITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867393#comment-17867393
]
Julian Hyde commented on CALCITE-6486:
--------------------------------------
This is what I call a "drill-a-hole" change. It may be a good idea. But those
implementations now become part of our public API and dependent projects (will
rightly) complain if we change them in future.
If there is a particular type of extensibility that you want to achieve, let's
discuss it. Subclassing the existing implementation may be the best way to
achieve it (for your project, and for Calcite, and for other projects that
depend on Calcite) but it may not.
> Make UnifyRule Implementations Public
> -------------------------------------
>
> Key: CALCITE-6486
> URL: https://issues.apache.org/jira/browse/CALCITE-6486
> Project: Calcite
> Issue Type: Wish
> Components: core
> Reporter: kate
> Priority: Trivial
>
> More and more database engines are now using and advancing materialised
> views. I've noticed that calcite hasn't been updated on this in a long time.
> We should make the rules exposed for external use and optimisation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
