[
https://issues.apache.org/jira/browse/HIVE-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629112#comment-16629112
]
Jaume M commented on HIVE-20556:
--------------------------------
[~ekoifman] this is a read-only field, since the user can't set it. I added
{{MTable.setId(long id) }} because I thought datanucleus used it to set {{id}}
but looks like it's using some sort of reflection. Looks like it can be removed
without consequence. This is the reason as well why {{i64 id}} is optional.
| I see tbl.unsetId() in a number of places. Could you explain what it's for?
This is because when we do:
{code}
Table tbl = ...
client.createTable(tbl);
Table tblRead = client.getTable(...);
Assert.asserEquals(tbl, tblRead);
{code}
The assert fails because tblRead has the id set. Therefore we remove it because
we don't want that to affect the comparison.
I've created: https://reviews.apache.org/r/68834/
> 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
> 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.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)
