You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 16:55:00 UTC
[jira] [Closed] (HBASE-6418) Minor bug in delete flow.
[ https://issues.apache.org/jira/browse/HBASE-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell closed HBASE-6418.
--------------------------------------
Assignee: (was: Laxman)
> Minor bug in delete flow.
> -------------------------
>
> Key: HBASE-6418
> URL: https://issues.apache.org/jira/browse/HBASE-6418
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0, 0.94.1, 0.94.2, 0.95.2
> Reporter: Laxman
> Priority: Major
>
> 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[])
> {code}
> 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()) {
> {code}
> Basically used a wrong API.
> kv.isDeleteType() should be KeyValue.isDelete(type);
--
This message was sent by Atlassian Jira
(v8.20.7#820007)