hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (Jira)" <>
Subject [jira] [Assigned] (HIVE-22728) Limit the scope of uniqueness of constraint name to database
Date Sat, 08 Feb 2020 01:02:34 GMT


Jesus Camacho Rodriguez reassigned HIVE-22728:

    Assignee: Miklos Gergely

> 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
> 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