asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-2301) Abort of DELETE operation is not handled properly
Date Thu, 01 Mar 2018 04:35:00 GMT


ASF subversion and git services commented on ASTERIXDB-2301:

Commit 38baf98605a50ca7edc37cff554d6006a8891680 in asterixdb's branch refs/heads/master from
[;h=38baf98 ]

[ASTERIXDB-2301][TX] Fix Abort of DELETE operation

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

- Fix the undo logic of the DELETE operation. Previously undo
of DELETE is implemented as re-inserting the old value. However,
if the deleted record is from the disk component, the old value could be
null. In this case, we simply need to physically deleted the anti-matter
key from the memory component, exactly the same as undo upsert.
- Add test cases for undo.

Change-Id: I5002d639399f024be8837da1c539101e6d62a159
Sonar-Qube: Jenkins <>
Reviewed-by: Michael Blow <>
Tested-by: Jenkins <>
Contrib: Jenkins <>
Integration-Tests: Jenkins <>

> Abort of DELETE operation is not handled properly
> -------------------------------------------------
>                 Key: ASTERIXDB-2301
>                 URL:
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: TX - Transactions
>            Reporter: Chen Luo
>            Assignee: Chen Luo
>            Priority: Critical
> The current abort of DELETE operation is simply re-inserting the old value. However,
the old value is logged only when the deleted record was found in the memory component. If
we delete a record which sits on the disk component, then old value is NULL and the abort
of the delete record is not handled correctly.

This message was sent by Atlassian JIRA

View raw message