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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/15 08:40:00 UTC

[jira] [Updated] (FLINK-12846) Carry primary key and unique key information in TableSchema

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

ASF GitHub Bot updated FLINK-12846:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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
>              Labels: pull-request-available
>             Fix For: 1.10.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
(v8.3.4#803005)