[
https://issues.apache.org/jira/browse/HBASE-21596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil updated HBASE-21596:
-----------------------------------------
Description:
Originally tested with HBase Shell delete command, but it's also reproducible
with Client API Delete operation.
was:
HBase Shell delete command is supposed to operate over an specific TS. If no TS
is informed, it will assume the latest TS for the cell and put delete marker
for it.
However, for a CF with VERSIONS => 1, if multiple puts were performed for same
cell, there may be multiple cell versions on the memstore, so delete would only
be "delete marking" one of those, and causing the most recent no marked one to
be shown on gets/scans, which then contradicts the CF "VERSIONS => 1"
configuration.
This issue is not seen with deleteall command or using Delete operation from
Java API.
> Delete for a specific cell version can bring back versions above VERSIONS
> limit
> -------------------------------------------------------------------------------
>
> Key: HBASE-21596
> URL: https://issues.apache.org/jira/browse/HBASE-21596
> Project: HBase
> Issue Type: Bug
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Minor
> Attachments: HBASE-21596-master.001.patch,
> HBASE-21596-master.002.patch, HBASE-21596-master.003.patch, initial-patch.txt
>
>
> Originally tested with HBase Shell delete command, but it's also reproducible
> with Client API Delete operation.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
