[
https://issues.apache.org/jira/browse/HBASE-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669772#comment-13669772
]
Ted Yu commented on HBASE-8626:
-------------------------------
Maybe we can introduce a special constant, Long.MIN_VALUE+1, e.g. which the
user can use for Delete's in the mutations.
HRegion would obtain now = System.currentTimeMillis() first.
When HRegion#doMiniBatchMutation() sees this special constant, it would wait
till System.currentTimeMillis() reaches now+1 (let's represent now+1 as
variable t). The Delete's would be given timestamp equal to t while the Put's
would receive timestamp now.
> RowMutations fail when Delete and Put on same columnFamily/column/row
> ---------------------------------------------------------------------
>
> Key: HBASE-8626
> URL: https://issues.apache.org/jira/browse/HBASE-8626
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.94.7, 0.95.0
> Environment: Ubuntu 12.04, HBase 0.94.7
> Reporter: Vinod
> Assignee: Ted Yu
> Fix For: 0.95.1
>
> Attachments: 8626-v1.txt, TestRowMutations.java,
> tests_for_row_mutations1.patch
>
>
> When RowMutations have a Delete followed by Put to same column family or
> columns or rows, only the Delete is happening while the Put is ignored so
> atomicity of RowMutations is broken for such cases.
> Attached is a unit test where the following tests are failing:
> - testDeleteCFThenPutInSameCF: Delete a column family and then Put to same
> column family.
> - testDeleteColumnThenPutSameColumn: Delete a column and then Put to same
> column.
> - testDeleteRowThenPutSameRow: Delete a row and then Put to same row
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
