[
https://issues.apache.org/jira/browse/OMID-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538145#comment-16538145
]
James Taylor commented on OMID-103:
-----------------------------------
Sorry for the confusion, [~ohads]. The scenario is:
* Insert a new row
* Commit the transaction
* Delete the row (forcing delete to be written to HBase)
* Insert a new row
* Attempt to commit the transaction (which will fail)
* Query the table and the delete will still be in effect even though the
commit failed
Maybe it is related to Omid not having a batch operation for its HTable
implementation, since in the above case the Delete and Put would come through
separate HBase calls?
> DeleteFamily marker still visible after rollback fails
> ------------------------------------------------------
>
> Key: OMID-103
> URL: https://issues.apache.org/jira/browse/OMID-103
> Project: Apache Omid
> Issue Type: Bug
> Reporter: James Taylor
> Priority: Major
>
> If a DeleteFamily marker is written to HBase and the subsequent abort of the
> transaction fails, the delete marker is still visible and mistakenly
> continues to take effect. For a repro, see
> TransactionIT.testFailureToRollbackAfterDelete() which passes for Tephra but
> fails for Omid.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
