hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14920) Compacting Memstore
Date Thu, 31 Mar 2016 06:32:25 GMT

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

Anoop Sam John commented on HBASE-14920:

Ya it is clear now why need the seqId update after in memory compaction also.. It helps when
many of the cells go away as a result of this. (Because of delete or version expiry etc)..
Ya make sense..  Pls add all these in code comments.  Ya was expecting this as the reason..
Just asked for confirm.

There is no problem in ur client code.  When we delete a row or a family fully, the type will
be *DeleteFamily*.  Ya the scanner deals with it as removes all cells of this row:cf with
TS less than the TS of this delete fam cell.  So u see this typed cell with low seqId?

> Compacting Memstore
> -------------------
>                 Key: HBASE-14920
>                 URL: https://issues.apache.org/jira/browse/HBASE-14920
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Eshcar Hillel
>            Assignee: Eshcar Hillel
>         Attachments: HBASE-14920-V01.patch, HBASE-14920-V02.patch, move.to.junit4.patch
> Implementation of a new compacting memstore with non-optimized immutable segment representation

This message was sent by Atlassian JIRA

View raw message