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 2019/01/23 20:09:00 UTC

[jira] [Commented] (HIVE-20556) Expose an API to retrieve the TBL_ID from TBLS in the metastore tables

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

Vihang Karajgaonkar commented on HIVE-20556:
--------------------------------------------

Hi [~ekoifman] [~jmarhuen] Sorry for commenting on this late. I was taking a look at this patch and I noticed that the fieldID of the thrift objects are being changed in this patch. Isn't that breaking on-the-wire-compatibility?

Also, since TBL_ID is dependent on backing database, aren't we leaking implementation into APIs here? http://www.datanucleus.org/products/accessplatform_4_2/jdo/value_generation.html says that the identity generation could be different based on how the datastore is configured. By exposing its type as a number i64 are we saying that we only support native identity generation?

> Expose an API to retrieve the TBL_ID from TBLS in the metastore tables
> ----------------------------------------------------------------------
>
>                 Key: HIVE-20556
>                 URL: https://issues.apache.org/jira/browse/HIVE-20556
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Standalone Metastore
>            Reporter: Jaume M
>            Assignee: Jaume M
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-20556.1.patch, HIVE-20556.10.patch, HIVE-20556.11.patch, HIVE-20556.12.patch, HIVE-20556.13.patch, HIVE-20556.14.patch, HIVE-20556.15.patch, HIVE-20556.16.patch, HIVE-20556.17.patch, HIVE-20556.18.patch, HIVE-20556.2.patch, HIVE-20556.3.patch, HIVE-20556.4.patch, HIVE-20556.5.patch, HIVE-20556.6.patch, HIVE-20556.7.patch, HIVE-20556.8.patch, HIVE-20556.9.patch
>
>
> We have two options to do this
> 1) Use the current MTable and add a field for this value
> 2) Add an independent API call to the metastore that would return the TBL_ID.
> Option 1 is preferable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)