[ 
https://issues.apache.org/jira/browse/HIVE-22728?focusedWorklogId=388408&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388408
 ]

ASF GitHub Bot logged work on HIVE-22728:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Feb/20 13:29
            Start Date: 17/Feb/20 13:29
    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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 388408)
    Time Spent: 20m  (was: 10m)

> Limit the scope of uniqueness of constraint name to table
> ---------------------------------------------------------
>
>                 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, 
> HIVE-22728.04.patch
>
>          Time Spent: 20m
>  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 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to