[
https://issues.apache.org/jira/browse/FLINK-12846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868170#comment-16868170
]
Hequn Cheng commented on FLINK-12846:
-------------------------------------
+1 for adding the key information! Primary key and unique key are part of
TableSchema and they are very helpful for the optimization.
BTW, how are we going to add the key infos? We may also need to consider other
information, like column nullable and computed column in order not to make the
TableSchema becoming more and more mussy.
What do you think?
Best, Hequn
> Carry primary key and unique key information in TableSchema
> -----------------------------------------------------------
>
> Key: FLINK-12846
> URL: https://issues.apache.org/jira/browse/FLINK-12846
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Jark Wu
> Assignee: Jark Wu
> Priority: Major
> Fix For: 1.9.0
>
>
> The primary key and unique key is a standard meta information in SQL. And
> they are important information for optimization, for example,
> AggregateRemove, AggregateReduceGrouping and state layout optimization for
> TopN and Join.
> So in this issue, we want to extend {{TableSchema}} to carry more information
> about primary key and unique keys. So that the TableSource can declare this
> meta information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
