Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 Aug 2014 05:17:12 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12734947.1408426387850.9921.1408684632049@arcas>
In-Reply-To: <JIRA.12734947.1408426387850@arcas>
References: <JIRA.12734947.1408426387850@arcas>
Subject: [jira] [Commented] (HBASE-11777) Find a way to use
 KV.setSequenceId() on Cells on the server-side read path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-11777:
-------------------------------

Makes sense Ram.

You know, servers-side, we have to be able to set the sequence id on the Cell/KV when writing at least (we set the sequenceid after we've written the WAL in ringbuffer event handler... see stampRegionSequenceId.  Its stamping a KV, not a Cell.  So its another place where we need to be able to set seqid on a Cell.

> Find a way to use KV.setSequenceId() on Cells on the server-side read path
> --------------------------------------------------------------------------
>
>                 Key: HBASE-11777
>                 URL: https://issues.apache.org/jira/browse/HBASE-11777
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.99.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: CellWithSequenceNumber.java
>
>
> Over in HBASE-11591 there was a need to set the sequenceId of the HFile to the bulk loaded KVs.  Since we are trying to use the concept of Cells in the read path if we need to use setSequenceId(), then the Cell has to be converted to KV and only KeyValue impl has the accessor setSequenceId().
> [~anoop.hbase] suggested if we can use a Server side impl of Cell and have these accessors in them.
> This JIRA aims to solve this and see the related code changes that needs to be carried out for this.


--
This message was sent by Atlassian JIRA
(v6.2#6252)