[HBASE-6418] Minor bug in delete flow.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 0.94.0, 0.94.1, 0.94.2, 0.95.2
• Assignee: Unassigned
• Reporter: Laxman
• Created: 18/Jul/12 04:09
• Updated: 13/Jun/22 16:54
• Resolved: 25/Jul/12 03:55

Description

Timestamp updation in Delete flow is not considering all flavors (Delete record, Delete Family, Delete Column) of Delete API. Currently its considering Delete Record only.

org.apache.hadoop.hbase.regionserver.HRegion.prepareDeleteTimestamps(Delete, byte[])

      for (KeyValue kv: kvs) {
        //  Check if time is LATEST, change to time of most recent addition if so
        //  This is expensive.
        if (kv.isLatestTimestamp() && kv.isDeleteType()) {

Basically used a wrong API.
kv.isDeleteType() should be KeyValue.isDelete(type);