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

Keith Turner commented on ACCUMULO-2817:
----------------------------------------

When doing code reviews, its nice to see what changes were made during the 
review.  Multiple commits provides one way to do this.  There are other ways.  
Would be nice to squash once the patch is ready to push.

> 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)

Reply via email to