You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Karen Coppage (Jira)" <ji...@apache.org> on 2019/12/06 16:25:00 UTC
[jira] [Assigned] (HIVE-22593) Dynamically partitioned MM
(insert-only ACID) table isn't compacting automatically
[ https://issues.apache.org/jira/browse/HIVE-22593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karen Coppage reassigned HIVE-22593:
------------------------------------
> Dynamically partitioned MM (insert-only ACID) table isn't compacting automatically
> ----------------------------------------------------------------------------------
>
> Key: HIVE-22593
> URL: https://issues.apache.org/jira/browse/HIVE-22593
> Project: Hive
> Issue Type: Bug
> Reporter: Karen Coppage
> Assignee: Karen Coppage
> Priority: Major
>
> Dynamic partitions of MM tables aren't entered into the HMS table TXN_COMPONENTS. On inserting into such tables we see this line in the HMS log:
> {code:java}
> Expected to move at least one record from txn_components to completed_txn_components when committing txn!{code}
> (This is not the case for non-partitioned MM tables.)
> Since the partitions aren't entered into COMPLETED_TXN_COMPONENTS, they aren't considered for automatic compaction.
> Probably the culprit is org.apache.hadoop.hive.ql.metadata.Hive#loadDynamicPartitions which has an isAcid parameter that is always false regarding MM tables, and also because MM tables' "write type" is AcidUtils.Operation.NOT_ACID and not INSERT.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)