[ https://issues.apache.org/jira/browse/HBASE-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108238#comment-16108238 ]
Biju Nair edited comment on HBASE-18471 at 8/1/17 1:10 AM: ----------------------------------------------------------- Another difference in {{scanner}} behavior, after the test code is run {code} hbase(main):023:0> scan 'test_dml' ROW COLUMN+CELL myRow column=myFamily:, timestamp=4, value=myValue myRow column=myFamily:myQualifier, timestamp=1, value=myValue 1 row(s) in 0.0330 seconds hbase(main):024:0> scan 'test_dml', {VERSIONS => 10} ROW COLUMN+CELL myRow column=myFamily:, timestamp=4, value=myValue myRow column=myFamily:, timestamp=3, value=myValue 1 row(s) in 0.0290 seconds {code} was (Author: gsbiju): Another difference in {{scanner}} behavior, after the test code is run ``` hbase(main):023:0> scan 'test_dml' ROW COLUMN+CELL myRow column=myFamily:, timestamp=4, value=myValue myRow column=myFamily:myQualifier, timestamp=1, value=myValue 1 row(s) in 0.0330 seconds hbase(main):024:0> scan 'test_dml', {VERSIONS => 10} ROW COLUMN+CELL myRow column=myFamily:, timestamp=4, value=myValue myRow column=myFamily:, timestamp=3, value=myValue 1 row(s) in 0.0290 seconds ``` > Deleted qualifier re-appearing after multiple puts. > --------------------------------------------------- > > Key: HBASE-18471 > URL: https://issues.apache.org/jira/browse/HBASE-18471 > Project: HBase > Issue Type: Bug > Components: Deletes, hbase, scan > Affects Versions: 1.3.0, 1.3.1 > Reporter: Thomas Martens > Attachments: HBaseDmlTest.java > > > The qualifier of a deleted row (with keep deleted cells true) re-appears > after re-inserting the same row multiple times (with different timestamp) > with an empty qualifier. > Scenario: > # Put row with family and qualifier (timestamp 1). > # Delete entire row (timestamp 2). > # Put same row again with family without qualifier (timestamp 3). > A scan (latest version) returns the row with family without qualifier, > version 3 (which is correct). > # Put the same row again with family without qualifier (timestamp 4). > A scan (latest version) returns multiple rows: > * the row with family without qualifier, version 4 (which is correct). > * the row with family with qualifier, version 1 (which is wrong). > There is a test scenario attached. > output: > <LOG> 13:42:53,952 [main] client.HBaseAdmin - Started disable of test_dml > <LOG> 13:42:55,801 [main] client.HBaseAdmin - Disabled test_dml > <LOG> 13:42:57,256 [main] client.HBaseAdmin - Deleted test_dml > <LOG> 13:42:58,592 [main] client.HBaseAdmin - Created test_dml > Put row: 'myRow' with family: 'myFamily' with qualifier: 'myQualifier' with > timestamp: '1' > Scan printout => > Row: 'myRow', Timestamp: '1', Family: 'myFamily', Qualifier: 'myQualifier', > Value: 'myValue' > Delete row: 'myRow' > Scan printout => > Put row: 'myRow' with family: 'myFamily' with qualifier: 'null' with > timestamp: '3' > Scan printout => > Row: 'myRow', Timestamp: '3', Family: 'myFamily', Qualifier: '', Value: > 'myValue' > Put row: 'myRow' with family: 'myFamily' with qualifier: 'null' with > timestamp: '4' > Scan printout => > Row: 'myRow', Timestamp: '4', Family: 'myFamily', Qualifier: '', Value: > 'myValue' > {color:red}Row: 'myRow', Timestamp: '1', Family: 'myFamily', Qualifier: > 'myQualifier', Value: 'myValue'{color} -- This message was sent by Atlassian JIRA (v6.4.14#64029)