[
https://issues.apache.org/jira/browse/HIVE-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750535#comment-16750535
]
Jaume M commented on HIVE-20556:
--------------------------------
bq. Older client thinks that field 2 is dbname while server has put tblName in
the field 2.
I understand this. My question was more in regards of what's the contract that
hive should promise: both old client works with new server and old server works
with new client?
Would this be solved by moving the id to the end of the table fields.
bq. 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.
I see, that's a good point.
I'll work on an addendum for this, thank you for looking into it.
> 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)
