Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 17 Jul 2016 03:50:20 +0000 (UTC)
From: "Xiang Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12915982.1448411965000.51860.1468727420573@Atlassian.JIRA>
In-Reply-To: <JIRA.12915982.1448411965000@Atlassian.JIRA>
References: <JIRA.12915982.1448411965000@Atlassian.JIRA> <JIRA.12915982.1448411965333@arcas>
Subject: [jira] [Commented] (HBASE-14881) Provide a Put API that uses the
 provided row without coping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 17 Jul 2016 03:50:28 -0000


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

Xiang Li commented on HBASE-14881:
----------------------------------

I think this enhancement does not apply to {{Put(ByteBuffer row)}} or {{Put(ByteBuffer row, long ts)}} either,because this.row takes the remaining part of the byte array which backs the ByteBuffer, right?

> Provide a Put API that uses the provided row without coping
> -----------------------------------------------------------
>
>                 Key: HBASE-14881
>                 URL: https://issues.apache.org/jira/browse/HBASE-14881
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jerry He
>            Assignee: Xiang Li
>         Attachments: HBASE-14881-master-v0.patch
>
>
> The current available Put API always makes a copy of the rowkey.
> Let's provide an API that accepts an immutable byte array as rowkey without making a copy.
> There are cases where the caller of Put has created the immutable byte array (e.g from a serializer) and will not change it for the Put duration. We can avoid making a copy again.


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