hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-23671) MSCK repair should handle transactional tables in certain usecases
Date Mon, 06 Jul 2020 16:08:00 GMT


ASF GitHub Bot logged work on HIVE-23671:

                Author: ASF GitHub Bot
            Created on: 06/Jul/20 16:07
            Start Date: 06/Jul/20 16:07
    Worklog Time Spent: 10m 
      Work Description: pvargacl commented on a change in pull request #1087:

File path: standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/
@@ -8322,6 +8322,22 @@ public AllocateTableWriteIdsResponse allocate_table_write_ids(
       return response;
+    @Override
+    public MaxAllocatedTableWriteIdResponse get_max_allocated_table_write_id(MaxAllocatedTableWriteIdRequest

Review comment:
       All the functions in HMS looks like this I don't want to break the pattern. On the
second glance, I had to change the seedWriteId and seedTxnId to look like this...

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 454923)
    Time Spent: 8h  (was: 7h 50m)

> MSCK repair should handle transactional tables in certain usecases
> ------------------------------------------------------------------
>                 Key: HIVE-23671
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Peter Varga
>            Assignee: Peter Varga
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 8h
>  Remaining Estimate: 0h
> The MSCK REPAIR tool does not handle transactional tables too well. It can find and add
new partitions the same way as for non-transactional tables, but since the writeId differences
are not handled, the data can not read back from the new partitions.
> We could handle some usecases when the writeIds in the HMS and the underlying data are
not conflicting. If the HMS does not contains allocated writes for the table we can seed the
table with the writeIds read from the directory structrure.
> Real life use cases could be:
>  * Copy data files from one cluster to another with different HMS, create the table and
>  * If the HMS db is lost, recreate the table and call MSCK REPAIR

This message was sent by Atlassian Jira

View raw message