[
https://issues.apache.org/jira/browse/CALCITE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189973#comment-17189973
]
Danny Chen commented on CALCITE-4215:
-------------------------------------
"We can have two metadata APIs"
I'm afraid this would complicates the code too much, it doubles the query
interfaces. I'm wondering if we can make a new component there to hold all the
defaults, the downstream project can plugin in their defaults so that they also
know what an unknown metadata returns.
It is not easy to plugin it into our existing {{MetadataHandler}} query APIs, i
have not thought it deeply yet.
> Ensure org.apache.calcite.schema.Statistic uses null vs emptyList
> appropriately
> -------------------------------------------------------------------------------
>
> Key: CALCITE-4215
> URL: https://issues.apache.org/jira/browse/CALCITE-4215
> Project: Calcite
> Issue Type: Sub-task
> Components: core
> Affects Versions: 1.25.0
> Reporter: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> null: statistic is *not* *known*
> emptyList: statistic is *known*, and the value is *empty* (e.g. no unique
> keys in the table)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
