You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "KIRTI RUGE (Jira)" <ji...@apache.org> on 2022/10/28 09:55:00 UTC
[jira] [Assigned] (HIVE-21154) Investigate using object IDs in Acid HMS schema instead of names
[ https://issues.apache.org/jira/browse/HIVE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
KIRTI RUGE reassigned HIVE-21154:
---------------------------------
Assignee: KIRTI RUGE
> Investigate using object IDs in Acid HMS schema instead of names
> ----------------------------------------------------------------
>
> Key: HIVE-21154
> URL: https://issues.apache.org/jira/browse/HIVE-21154
> Project: Hive
> Issue Type: New Feature
> Components: Transactions
> Affects Versions: 1.0.0
> Reporter: Eugene Koifman
> Assignee: KIRTI RUGE
> Priority: Major
>
> Currently all Acid related tables in HMS DB (HIVE_LOCKS, TXN_COMPONENTS, etc) use db_name/table_name/partition_name to identify the metastore object that is being tracked (these are potentially long strings, esp partition name. It would improve perf to use object ID such as TBLS.TBL_ID which is exposed in Thrift since HIVE-20556. It would also make handling object rename operations no-op (currently handled in {{TxnHandler.onRename()}} from {{AcidEventListener extends MetaStoreEventListener}}). This would require significant HMS schema changes and surfacing the ID of Database/Partition objects.
> Need to think how this affects replication.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)