[
https://issues.apache.org/jira/browse/FLINK-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he closed FLINK-21710.
------------------------------
Resolution: Fixed
Fixed in 1.13.0: 0297b849ee2ab0c96bb60f585a71a04c6b9c0f97
Fixed in 1.12.3: feaa9a6b10553fd44f11987cb564fb808a7a53b5
> FlinkRelMdUniqueKeys gets incorrect result on TableScan after project
> push-down
> -------------------------------------------------------------------------------
>
> Key: FLINK-21710
> URL: https://issues.apache.org/jira/browse/FLINK-21710
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0, 1.12.3
>
>
> FlinkRelMdUniqueKeys#getTableUniqueKeys uses the original columns to find the
> index of primary keys. But after project push-down, the indexes is incorrect
> based on original columns, and the new columns should be used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
