You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Wang Yanlin (Jira)" <ji...@apache.org> on 2019/11/04 11:29:00 UTC

[jira] [Updated] (CALCITE-3473) Getting unique result for table scan should contain key column(s)

     [ https://issues.apache.org/jira/browse/CALCITE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wang Yanlin updated CALCITE-3473:
---------------------------------
    Summary: Getting unique result for table scan should contain key column(s)  (was: Result of getting unique result for table scan should contain key column(s))

> Getting unique result for table scan should contain key column(s)
> -----------------------------------------------------------------
>
>                 Key: CALCITE-3473
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3473
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Wang Yanlin
>            Assignee: Wang Yanlin
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently,   *mq.getUniqueKeys()*  for  *TableScan* returns empty.
> However, for table with key column(s) defined, we can refer uniqueness on key column(s), so the result should contain key column(s)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)