[
https://issues.apache.org/jira/browse/CALCITE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967190#comment-16967190
]
Wang Yanlin commented on CALCITE-3473:
--------------------------------------
# Yes, using powerSet will have performance issue if column number is big. I
add an API to get unique keys for table. Is that OK?
# Yes, the refactor of test case does not woks for RelNode. Actually, I just
want to remove duplicate codes for checking with sql string, because they have
same logic. For other case that checks unique keys using RelNode, like
*testCorrelateUniqueKeys*, there seem to have some special check logic inside,
so I keep it unchanged.
> 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)
