[
https://issues.apache.org/jira/browse/HIVE-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750515#comment-16750515
]
Vihang Karajgaonkar commented on HIVE-20556:
--------------------------------------------
{quote}Isn't that breaking on-the-wire-compatibility?
What is the compatibility that should be preserved? Hive can be upgraded while
the metastore remain the same? So new client should be able to speak to old
server.
{quote}
For example, when metastore is upgraded, the older clients will not be able to
deserialize the table objects since they both have different interpretations of
the deserialized byte stream. Older client thinks that field 2 is dbname while
server has put tblName in the field 2.
{quote}
The purpose of exposing this was for the client to be able to submit the table
id in this ticket HIVE-20538. What would be the problem here? The client could
figure out what database is being used by analyzing the ids?
{quote}
I totally am on the same page. We need object id for make use-cases. However,
by defining the id as a int64 we have committed to a numeric identity instead
of lets say a uuid which would be globally unique. If we had defined the type
of the id in the thrift interface as string we could have potentially switched
to a uuid based id.
> 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)
