hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (Jira)" <>
Subject [jira] [Updated] (HIVE-22593) Dynamically partitioned MM (insert-only ACID) tables don't compact automatically
Date Thu, 09 Jan 2020 13:46:00 GMT


Peter Vary updated HIVE-22593:
    Fix Version/s: 4.0.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Pushed to master.
Thanks for the patch [~klcopp]!

> Dynamically partitioned MM (insert-only ACID) tables don't compact automatically
> --------------------------------------------------------------------------------
>                 Key: HIVE-22593
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Karen Coppage
>            Assignee: Karen Coppage
>            Priority: Major
>             Fix For: 4.0.0
>         Attachments: HIVE-22593.01.patch, HIVE-22593.01.patch, HIVE-22593.02.patch, HIVE-22593.03.patch,
HIVE-22593.04.patch, HIVE-22593.04.patch
> 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

View raw message