You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Danny Chen (Jira)" <ji...@apache.org> on 2020/09/03 07:36:00 UTC
[jira] [Comment Edited] (CALCITE-4215) Ensure
org.apache.calcite.schema.Statistic uses null vs emptyList appropriately
[ https://issues.apache.org/jira/browse/CALCITE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189895#comment-17189895 ]
Danny Chen edited comment on CALCITE-4215 at 9/3/20, 7:35 AM:
--------------------------------------------------------------
Like Flink do, what about -1, because row count expect to be positive, -1 means *unknown*.
Oops, the latest code changes to {{1E8}} in order to avoid broadcast join.
was (Author: danny0405):
Like Flink do, what about -1, because row count expect to be positive, -1 means *unknown*.
> 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)