You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Matt Dailey (JIRA)" <ji...@apache.org> on 2015/02/18 06:18:11 UTC
[jira] [Updated] (ACCUMULO-2817) Add offset and limit arguments to
byte array Encoder.decode method
[ https://issues.apache.org/jira/browse/ACCUMULO-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Dailey updated ACCUMULO-2817:
----------------------------------
Affects Version/s: 1.7.0
Status: Patch Available (was: Open)
Rebased against origin/master at commit 990dafb. {{mvn clean test}} passed including new unit tests that are part of the patch.
Any feedback welcome!
> 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
> Affects Versions: 1.7.0
> Reporter: Josh Elser
> 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)