[
https://issues.apache.org/jira/browse/CALCITE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189874#comment-17189874
]
Danny Chen commented on CALCITE-4215:
-------------------------------------
I agree
"This is interesting to know because numeric nulls should be relatively easy to
detect with IDE."
But we can not rely on the IDE to keep good code quality. The code itself
should be defensive somehow.
I also like the idea
"RelMetadataQuery users don't need to deal with null distributions."
It is much better if we can return a default value when we can not infer the
metadata, especially if with such a default value, the engine have a
deterministic behavior (it knows how to go ahead with it).
> 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)
