Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1FF8210678 for ; Sun, 22 Feb 2015 00:12:12 +0000 (UTC) Received: (qmail 10163 invoked by uid 500); 22 Feb 2015 00:12:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 10122 invoked by uid 500); 22 Feb 2015 00:12:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 10105 invoked by uid 99); 22 Feb 2015 00:12:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Feb 2015 00:12:11 +0000 Date: Sun, 22 Feb 2015 00:12:11 +0000 (UTC) From: "Matt Dailey (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2817) Add offset and limit arguments to byte array Encoder.decode method MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Dailey updated ACCUMULO-2817: ---------------------------------- Attachment: (was: ACCUMULO-2817.patch) > Add offset and limit arguments to byte array Encoder.decode method > ------------------------------------------------------------------ > > Key: ACCUMULO-2817 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2817 > Project: Accumulo > Issue Type: Improvement > Components: client > Reporter: Josh Elser > Assignee: Matt Dailey > Labels: newbie > Fix For: 1.7.0 > > Attachments: ACCUMULO-2817.patch > > > Similar to ACCUMULO-2445, but presently the encoder only works on complete byte arrays. This forces an extra copy of the data when it is located in an array that contains other information (e.g. a composite key). > It would be nice to be able to provide offset and length arguments to {{Encoder.decode}} so that users can avoid the additional arraycopy. > Changing to a ByteBuffer instead of byte array argument would also be acceptable, but more churn on the API that, unless it's happening globally, I would rather avoid. It would also incur the penalty for that extra Object, which while minimal alone, could be significant if decoding every value in a table, for example. -- This message was sent by Atlassian JIRA (v6.3.4#6332)