[ https://issues.apache.org/jira/browse/ACCUMULO-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346983#comment-15346983 ]
Josh Elser commented on ACCUMULO-2817: -------------------------------------- bq. Hi folks, I'm interested in calling decodeUnchecked(byte[], off, len) as public API, since it removes the need to copy a subarray out from a larger array. Can we pull this discussion into another JIRA issue, [~dhutchis]? It would get confusing to track since this changeset was already released in 1.7.0. > 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 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)