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

Posted to issues@calcite.apache.org by "Haisheng Yuan (Jira)" <ji...@apache.org> on 2019/12/03 22:22:00 UTC

[jira] [Resolved] (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 ]

Haisheng Yuan resolved CALCITE-3473.
------------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in https://github.com/apache/calcite/commit/ed181a4671b9941f2852c581daa043d8a2d6dec2. Thanks for the PR, [~yanlin-Lynn]!

> 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
>             Fix For: 1.22.0
>
>          Time Spent: 1.5h
>  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)