[HIVE-22728] Limit the scope of uniqueness of constraint name to table

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Labels: pull-request-available
• Assignee: Miklos Gergely
• Reporter: Jesús Camacho Rodríguez
• Created: 14/Jan/20 21:21
• Updated: 27/Feb/24 22:23
• Resolved: 17/Feb/20 13:29

Description

Currently, constraint names are globally unique across all databases (assumption is that this may have done by design). Nevertheless, though behavior seems to be implementation specific, it would be interesting to limit the scope to uniqueness per table.
To change the scope to one table, we would need to add the PARENT_TABLE_ID in the KEY_CONSTRAINTS table to the PRIMARY KEY of that table. Some minor changes to the error messages would be needed too, since otherwise it would be difficult to identify the correct violation in queries that span across multiple databases. Additionally, the SQL scripts will need to be updated to update the PRIMARY KEY.

Issue Links

• links to: GitHub Pull Request #906