[
https://issues.apache.org/jira/browse/HIVE-20137?focusedWorklogId=495282&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-495282
]
ASF GitHub Bot logged work on HIVE-20137:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/20 11:49
Start Date: 05/Oct/20 11:49
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on a change in pull request #1532:
URL: https://github.com/apache/hive/pull/1532#discussion_r499536263
##########
File path: ql/src/java/org/apache/hadoop/hive/ql/io/AcidUtils.java
##########
@@ -2999,6 +2980,10 @@ Seems much cleaner if each stmt is identified as a
particular HiveOperation (whi
compBuilder.setExclusive();
compBuilder.setOperationType(DataOperationType.NO_TXN);
break;
+ case DDL_EXCL_WRITE:
+ compBuilder.setExclWrite();
Review comment:
ExclWrite is gonna block concurrent reads. Is it expected?
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 495282)
Time Spent: 1h (was: 50m)
> Truncate for Transactional tables should use base_x
> ---------------------------------------------------
>
> Key: HIVE-20137
> URL: https://issues.apache.org/jira/browse/HIVE-20137
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: Peter Varga
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This is a follow up to HIVE-19387.
> Once we have a lock that blocks writers but not readers (HIVE-19369), it
> would make sense to make truncate create a new base_x, where is x is a
> writeId in current txn - the same as Insert Overwrite does.
> This would mean it can work w/o interfering with existing writers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
