[jira] [Commented] (HBASE-21596) HBase Shell "delete" command can cause older versions to be shown even if VERSIONS is configured as 1

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

Sean Busbey commented on HBASE-21596:
-------------------------------------

shouldn't the delete marked cell count towards the number of versions? I think if we did that then the rest of the scanner mechanisms you mention would behave correctly?

> HBase Shell "delete" command can cause older versions to be shown even if VERSIONS is configured as 1
> -----------------------------------------------------------------------------------------------------
>
>                 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
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)