hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15413) Primary key constraints forced to be unique across database and table names
Date Mon, 12 Dec 2016 19:01:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742801#comment-15742801
] 

Ashutosh Chauhan commented on HIVE-15413:
-----------------------------------------

Thing to keep in mind here is unlike other databases, Hive does allow referencing tables from
different databases in a single query, so making constraint name unique may have consequences
to that.

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

Mime
View raw message