You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Chen Luo (JIRA)" <ji...@apache.org> on 2018/10/23 21:43:01 UTC

[jira] [Created] (ASTERIXDB-2467) Concurrency control protocol is not correct when there are bad tuples

Chen Luo created ASTERIXDB-2467:
-----------------------------------

             Summary: Concurrency control protocol is not correct when there are bad tuples
                 Key: ASTERIXDB-2467
                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2467
             Project: Apache AsterixDB
          Issue Type: Bug
          Components: STO - Storage
            Reporter: Chen Luo


The current deadlock-free locking protocol pushes partial frames when the try locking fails. However, when there are bad tuples (e.g., duplicates) in the frame, the state of partial frames is always reset after the bad tuple is removed from frame.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)