hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8626) RowMutations fail when Delete and Put on same columnFamily/column/row
Date Wed, 29 May 2013 05:00:23 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668996#comment-13668996
] 

Lars Hofhansl commented on HBASE-8626:
--------------------------------------

-1 on changing this. This is working as designed.

It does not make any logical sense to do an atomic Put and Delete to the *same* column. What
does that even mean? You want both the Put and the Delete, but not really the Put, because
the Delete should win.

Will close as "Won't fix" unless I hear objections.
                
> 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.94.7, 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

Mime
View raw message