[
https://issues.apache.org/jira/browse/FLINK-16195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323077#comment-17323077
]
Flink Jira Bot commented on FLINK-16195:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Append constant fields to unique key set when deriving unique keys in
> FlinkRelMdUniqueKeys on project
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-16195
> URL: https://issues.apache.org/jira/browse/FLINK-16195
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Major
> Labels: stale-assigned
>
> currently, {{FlinkRelMdUniqueKeys}} only supports deriving unique keys on
> non-constant fields. such as: {{select a, b, 1, count( * ) from T group by a,
> b}}, currently the derived unique keys is {{a, b}}. However {{a, b, 1}} is
> also a unique key, and the result is {{a, b}} and {{a, b, 1}}.
> note: Ideally, the planner does not require the constant key in the unique
> key set, all constant values are pulled up or removed as much as possible.
> Supports this improvement to handle some corner cases in cbo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
