You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/12 22:39:01 UTC
[jira] [Updated] (FLINK-15123) remove uniqueKeys from FlinkStatistic in blink planner
[ https://issues.apache.org/jira/browse/FLINK-15123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-15123:
-----------------------------------
Labels: stale-major starter (was: starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> 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: stale-major, starter
> 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.10#820010)