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

Posted to issues@calcite.apache.org by "Vladimir Sitnikov (Jira)" <ji...@apache.org> on 2020/01/02 16:58:00 UTC

[jira] [Updated] (CALCITE-3666) Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc

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

Vladimir Sitnikov updated CALCITE-3666:
---------------------------------------
    Summary: Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc  (was: Refine RelMdColumnUniqueness for Calc)

> Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc
> ---------------------------------------------------------
>
>                 Key: CALCITE-3666
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3666
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.21.0
>            Reporter: Vladimir Sitnikov
>            Assignee: Vladimir Sitnikov
>            Priority: Major
>
> RelMdColumnUniqueness does not have an override for Calc, thus it can't resolve uniqueness for EnumerableCalc
> In practice, it is hard to deduce uniqueness for select emp.id*emp.deptno from emp, however, simple projects can be resolved (e.g. when Calc selects one of its input as is).



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