[
https://issues.apache.org/jira/browse/CALCITE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864663#comment-15864663
]
Julian Hyde commented on CALCITE-1631:
--------------------------------------
It's not practical to call {{RelOptTable.isKey(ImmutableBitSet columns)}} for
each set of columns: there are 2 ^ N such combinations if a table has N
columns, then you need to pare those down to the minimal keys. If you have a
table that knows what its keys are, it's better to implement a metadata
provider for that table.
> 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)
