tree 2709e0b53c98f177c6361f6195c7fac49f8771f2
parent 11d5b2812ff304af77f548979a08ee5998e45d48
author luochen <cluo8@uci.edu> 1540332982 -0700
committer Luo Chen <cluo8@uci.edu> 1540421328 -0700

[ASTERIXDB-2467][STO] Fix locking protocol with bad tuples

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- The current locking protocol is not correct when there are bad tuples,
e.g., duplicates. When locking fails, the write must push partial frames
so that the previous acquired locks are released. However, if there are
bad tuples in the frame, after bad tuples are removed from the frame, the
state of pushed partial frames will be completely lost.

Change-Id: I86baa1f21ef7390777c8e2b0ce226095528e7f18
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3003
Reviewed-by: Xikui Wang <xkkwww@gmail.com>
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mhubail@apache.org>