Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 25 May 2015 11:45:17 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12832330.1432367734000.21592.1432554317483@Atlassian.JIRA>
In-Reply-To: <JIRA.12832330.1432367734000@Atlassian.JIRA>
References: <JIRA.12832330.1432367734000@Atlassian.JIRA>
 <JIRA.12832330.1432367734631@arcas>
Subject: [jira] [Commented] (HBASE-13754) Allow non KeyValue Cell types also
 to oswrite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ramkrishna.s.vasudevan commented on HBASE-13754:
------------------------------------------------

+1

> Allow non KeyValue Cell types also to oswrite
> ---------------------------------------------
>
>                 Key: HBASE-13754
>                 URL: https://issues.apache.org/jira/browse/HBASE-13754
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13754.patch
>
>
> While making the cellblock for returning data to client, we have to write the cell data into an OutputStream. KeyValue has a static oswrite() method with which it can write data in one go. (KeyValue components are in a single byte[]). For other cell implementation, we will call getXXXLength() and getXXXArray() and write each component one after the other. This is not efficient as the KeyValue way. In fact other cell impls also may have one contigous byte[] backing for keys atleast. (See ClonedSeekerState) We can optimize for such Cells also.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)