hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-22728) Limit the scope of uniqueness of constraint name to database
Date Tue, 11 Feb 2020 13:54:00 GMT


Hive QA commented on HIVE-22728:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 17990 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[resourceplan] (batchId=179)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[schq_materialized] (batchId=181)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb] (batchId=175)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb_schq] (batchId=180)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 6 tests failed

This message is automatically generated.

ATTACHMENT ID: 12993088 - PreCommit-HIVE-Build

> Limit the scope of uniqueness of constraint name to database
> ------------------------------------------------------------
>                 Key: HIVE-22728
>                 URL:
>             Project: Hive
>          Issue Type: Wish
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Miklos Gergely
>            Priority: Major
>         Attachments: HIVE-22728.01.patch
> 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

View raw message