[
https://issues.apache.org/jira/browse/HIVE-22728?focusedWorklogId=385772&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-385772
]
ASF GitHub Bot logged work on HIVE-22728:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Feb/20 09:51
Start Date: 12/Feb/20 09:51
Worklog Time Spent: 10m
Work Description: miklosgergely commented on pull request #906:
HIVE-22728 Limit the scope of uniqueness of constraint name to database
URL: https://github.com/apache/hive/pull/906
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 385772)
Remaining Estimate: 0h
Time Spent: 10m
> Limit the scope of uniqueness of constraint name to database
> ------------------------------------------------------------
>
> Key: HIVE-22728
> URL: https://issues.apache.org/jira/browse/HIVE-22728
> Project: Hive
> Issue Type: Wish
> Reporter: Jesus Camacho Rodriguez
> Assignee: Miklos Gergely
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-22728.01.patch, HIVE-22728.02.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 database.
> Currently we do not store database information with the constraints. To
> change the scope to one db, we would need to store the DB_ID in the
> KEY_CONSTRAINTS table in metastore when we create a constraint and add the
> DB_ID 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 populate
> the DB_ID when we upgrade to new version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
