You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ling Jin (Jira)" <ji...@apache.org> on 2022/04/22 15:43:00 UTC
[jira] [Commented] (FLINK-15123) remove uniqueKeys from FlinkStatistic in blink planner
[ https://issues.apache.org/jira/browse/FLINK-15123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526503#comment-17526503 ]
Ling Jin commented on FLINK-15123:
----------------------------------
It seems the issue has no progress for a long time, I would have a try.
I am going to walking the code for now, and feedback if I find the clue for how to solve this.
> remove uniqueKeys from FlinkStatistic in blink planner
> -------------------------------------------------------
>
> Key: FLINK-15123
> URL: https://issues.apache.org/jira/browse/FLINK-15123
> Project: Flink
> Issue Type: Technical Debt
> Components: Table SQL / Planner
> Reporter: godfrey he
> Priority: Major
> Labels: starter
> Fix For: 1.16.0
>
> Attachments: b_5.txt
>
>
> {{uniqueKeys}} is a kind of constraint, it's unreasonable that {{uniqueKeys}} is a kind of statistic. so we should remove uniqueKeys from {{FlinkStatistic}} in blink planner. Some temporary solutions (e.g. {{RichTableSourceQueryOperation}}) should also be resolved after primaryKey is introduced in {{TableSchema}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)