[ 
https://issues.apache.org/jira/browse/HIVE-23503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111534#comment-17111534
 ] 

Hive QA commented on HIVE-23503:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13003381/HIVE-23503.1.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17275 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/22464/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/22464/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-22464/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 13003381 - PreCommit-HIVE-Build

> ValidTxnManager doesn't consider txns opened and committed between snapshot 
> generation and locking when evaluating ValidTxnListState
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-23503
>                 URL: https://issues.apache.org/jira/browse/HIVE-23503
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>            Reporter: Denys Kuzmenko
>            Assignee: Denys Kuzmenko
>            Priority: Major
>         Attachments: HIVE-23503.1.patch
>
>
> ValidTxnManager doesn't consider txns opened and committed between snapshot 
> generation and locking when evaluating ValidTxnListState. This cause issues 
> like duplicate insert in case of concurrent merge insert & insert.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to