[
https://issues.apache.org/jira/browse/CALCITE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773749#comment-16773749
]
godfrey he commented on CALCITE-2855:
-------------------------------------
I had checked -CALCITE-1812-, and i want the behavior of extended
RelMetadataQuery to be consistent with default RelMetadataQuery. The intent of
`override RelOptCluster#getMetadataQuery` is same as the intent of CALCITE-1812.
Back to the above example, RelMetadataQuery instance is always from extented
RelOptCluster#getMetadataQuery, so we can cast the instance to extended
RelMetadataQuery to call ColumnInterval in Selectivity (the return type of
getMetadataQuery is `RelMetadataQuery`).
> Make RelOptCluster constructor public
> -------------------------------------
>
> Key: CALCITE-2855
> URL: https://issues.apache.org/jira/browse/CALCITE-2855
> Project: Calcite
> Issue Type: Improvement
> Reporter: godfrey he
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Expose RelOptCluster Constructor outside package to allow override.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
