[
https://issues.apache.org/jira/browse/HIVE-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Kuzmenko updated HIVE-24211:
----------------------------------
Fix Version/s: 4.0.0-alpha-1
> Replace Snapshot invalidate logic with WriteSet check for txn conflict
> detection
> --------------------------------------------------------------------------------
>
> Key: HIVE-24211
> URL: https://issues.apache.org/jira/browse/HIVE-24211
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Reporter: Denys Kuzmenko
> Assignee: Denys Kuzmenko
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> *Issue with concurrent writes on partitioned table:*
> Concurrent writes on different partitions should execute in parallel without
> issues. They acquire a shared lock on table level and exclusive write on
> partition level (hive.txn.xlock.write=true).
> However there is a problem with the Snapshot validation. It compares valid
> writeIds seen by current transaction, recorded before locking, with the
> actual list of writeIds. The Issue is that writeId in Snapshot has no
> information on partition, meaning that concurrent writes to different
> partitions would be seen as writes to the same non-partitioned table causing
> Snapshot to be obsolete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
