[
https://issues.apache.org/jira/browse/CALCITE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864737#comment-15864737
]
Julian Hyde commented on CALCITE-1631:
--------------------------------------
Because we have a much better mechanism: if you have the keys (or any one of a
dozen other kinds of metadata), define a metadata provider.
> RelMdUniqueKeys doesn't handle TableScan
> ----------------------------------------
>
> Key: CALCITE-1631
> URL: https://issues.apache.org/jira/browse/CALCITE-1631
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Jess Balint
> Assignee: Julian Hyde
> Priority: Minor
>
> In contrast to {{RelMdColumnUniqueness}}, which delegates to
> {{RelOptTable.isKey()}}, {{RelMdUniqueKeys}} does not handle a {{TableScan}}.
> This can be fixed by exposing the unique keys via the {{RelOptTable}}
> interface and delegating the call in the same fashion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
