[
https://issues.apache.org/jira/browse/HIVE-23671?focusedWorklogId=455352&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-455352
]
ASF GitHub Bot logged work on HIVE-23671:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jul/20 11:10
Start Date: 07/Jul/20 11:10
Worklog Time Spent: 10m
Work Description: pvargacl commented on a change in pull request #1087:
URL: https://github.com/apache/hive/pull/1087#discussion_r450785863
##########
File path:
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnHandler.java
##########
@@ -2015,8 +2019,49 @@ public AllocateTableWriteIdsResponse
allocateTableWriteIds(AllocateTableWriteIds
return allocateTableWriteIds(rqst);
}
}
+
+ @Override
+ public MaxAllocatedTableWriteIdResponse
getMaxAllocatedTableWrited(MaxAllocatedTableWriteIdRequest rqst) throws
MetaException {
+ String dbName = rqst.getDbName();
+ String tableName = rqst.getTableName();
+ try {
+ Connection dbConn = null;
+ PreparedStatement pStmt = null;
+ ResultSet rs = null;
+ try {
+ lockInternal();
Review comment:
fixed
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 455352)
Time Spent: 10h 50m (was: 10h 40m)
> MSCK repair should handle transactional tables in certain usecases
> ------------------------------------------------------------------
>
> Key: HIVE-23671
> URL: https://issues.apache.org/jira/browse/HIVE-23671
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Peter Varga
> Assignee: Peter Varga
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10h 50m
> 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 call MSCK REPAIR
> * If the HMS db is lost, recreate the table and call MSCK REPAIR
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
