[ https://issues.apache.org/jira/browse/CALCITE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190043#comment-17190043 ]
Danny Chen commented on CALCITE-4215: ------------------------------------- Yes, i think i got your idea, and the query interfaces doubled, user also need to choose to use which one. > 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)