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

Posted to issues@hive.apache.org by "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2020/06/30 18:08:00 UTC

[jira] [Assigned] (HIVE-23785) Database should have a unique id

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

Vihang Karajgaonkar reassigned HIVE-23785:
------------------------------------------


> Database should have a unique id
> --------------------------------
>
>                 Key: HIVE-23785
>                 URL: https://issues.apache.org/jira/browse/HIVE-23785
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>
> HIVE-20556 introduced a id field to the Table object. This is a useful information since a table which is dropped and recreated with the same name will have a different Id. If a HMS client is caching such table object, it can be used to determine if the table which is present on the client-side matches with the one in the HMS.
> We can expand this idea to other HMS objects like Database, Catalogs and Partitions and add a new id field.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)