[
https://issues.apache.org/jira/browse/HIVE-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941911#comment-15941911
]
Pengcheng Xiong commented on HIVE-15413:
----------------------------------------
I am deferring this to Hive 3.0 as we are going to cut the first RC and it is
not marked as blocker. Please feel free to commit to the branch if this can be
resolved before the release.
> 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.15#6346)
