You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2016/12/09 23:55:58 UTC

[jira] [Updated] (HIVE-15413) Primary key constraints forced to be unique across database and table names

     [ https://issues.apache.org/jira/browse/HIVE-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thejas M Nair updated HIVE-15413:
---------------------------------
    Target Version/s: 2.2.0

> Primary key constraints forced to be unique across database and table names
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-15413
>                 URL: https://issues.apache.org/jira/browse/HIVE-15413
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 2.2.0
>            Reporter: Alan Gates
>            Priority: Critical
>
> In the RDBMS underlying the metastore the table that stores primary and foreign keys has it's own primary key (at the RDBMS level) of (constraint_name, position).  This means that a constraint name must be unique across all tables and databases in a system.  This is not reasonable.  Database and table name should be included in the RDBMS primary key.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)