[
https://issues.apache.org/jira/browse/HIVE-22728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037707#comment-17037707
]
Hive QA commented on HIVE-22728:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12993519/HIVE-22728.04.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20662/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20662/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20662/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12993519/HIVE-22728.04.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12993519 - PreCommit-HIVE-Build
> 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: 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 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)
