[ https://issues.apache.org/jira/browse/FLINK-33666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther closed FLINK-33666. -------------------------------- Fix Version/s: 1.19.0 Resolution: Fixed Fixed in master: ca1c7ce48127472a7c7965099f8a7227549f09df > MergeTableLikeUtil uses different constraint name than Schema > ------------------------------------------------------------- > > Key: FLINK-33666 > URL: https://issues.apache.org/jira/browse/FLINK-33666 > Project: Flink > Issue Type: Bug > Components: Table SQL / Planner > Affects Versions: 1.18.0 > Reporter: Timo Walther > Assignee: Jeyhun Karimov > Priority: Major > Labels: pull-request-available > Fix For: 1.19.0 > > > {{MergeTableLikeUtil}} uses a different algorithm to name constraints than > {{Schema}}. > {{Schema}} includes the column names. > {{MergeTableLikeUtil}} uses a hashCode which means it might depend on JVM > specifics. > For consistency we should use the same algorithm. I propose to use > {{Schema}}'s logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)