Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 16 Nov 2013 01:20:18 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12675544.1382641253548.84341.1384564818292@arcas>
In-Reply-To: <JIRA.12675544.1382641253548@arcas>
References: <JIRA.12675544.1382641253548@arcas>
Subject: [jira] [Commented] (HBASE-9834) Minimize byte[] copies for 'smart'
 clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-9834:
---------------------------------------

{quote}
I now wonder how we can write a test to catch these.
Maybe generate a file will all kinds of a objects, save that. Then
read that back
regenerate and make sure it's identical
that way we ensured that neither readFields nor write has changed.
{quote}

Ok, HBASE-9981

> Minimize byte[] copies for 'smart' clients
> ------------------------------------------
>
>                 Key: HBASE-9834
>                 URL: https://issues.apache.org/jira/browse/HBASE-9834
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.94.15
>
>         Attachments: hbase-9834-0.94-v0.patch, hbase-9834-0.94-v1.patch, hbase-9834-0.94-v2.patch, hbase-9834-0.94-v3.patch
>
>
> 'Smart' clients (e.g. phoenix) that have in-depth knowledge of HBase often bemoan the extra byte[] copies that must be done when building multiple puts/deletes. We should provide a mechanism by which they can minimize these copies, but still remain wire compatible. 


--
This message was sent by Atlassian JIRA
(v6.1#6144)