hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-24211) Replace Snapshot invalidate logic with WriteSet check for txn conflict detection
Date Thu, 01 Oct 2020 07:50:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-24211?focusedWorklogId=493328&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-493328
]

ASF GitHub Bot logged work on HIVE-24211:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Oct/20 07:49
            Start Date: 01/Oct/20 07:49
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ commented on pull request #1533:
URL: https://github.com/apache/hive/pull/1533#issuecomment-701956664


   @jcamachor , could you please review 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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 493328)
    Time Spent: 40m  (was: 0.5h)

> 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
>          Time Spent: 40m
>  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.3.4#803005)

Mime
View raw message