[FLINK-21710] FlinkRelMdUniqueKeys gets incorrect result on TableScan after project push-down

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.13.0, 1.12.3
• Component/s: Table SQL / Planner
• Labels: pull-request-available
• Assignee: godfrey he
• Reporter: godfrey he
• Created: 10/Mar/21 09:30
• Updated: 25/Jun/21 02:39
• Resolved: 15/Mar/21 02:36

Description

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.

Issue Links

• relates to: FLINK-23135 Flink SQL Error while applying rule AggregateReduceGroupingRule
• links to: GitHub Pull Request #15138
• links to: GitHub Pull Request #15163