You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2017/04/04 16:51:41 UTC

[jira] [Updated] (HIVE-15724) getPrimaryKeys and getForeignKeys in metastore does not normalize db and table name

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

Ashutosh Chauhan updated HIVE-15724:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Pushed to master. Thanks, Daniel!

> getPrimaryKeys and getForeignKeys in metastore does not normalize db and table name
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-15724
>                 URL: https://issues.apache.org/jira/browse/HIVE-15724
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 3.0.0
>
>         Attachments: HIVE-15724.1.patch, HIVE-15724.2.patch
>
>
> In db, everything is lower case. When we retrieve constraints back, we need to normalize dbname/tablename. Otherwise, the following sample script fail:
> alter table Table9 add constraint pk1 primary key (a) disable novalidate;
> ALTER TABLE Table9 drop constraint pk1;
> Error message: InvalidObjectException(message:The constraint: pk1 does not exist for the associated table: default.Table9



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)