[
https://issues.apache.org/jira/browse/HBASE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729846#comment-13729846
]
Nick Dimiduk commented on HBASE-9091:
-------------------------------------
Yes, it does show through on the API. I consider it "sugar" at this point
because the same features are supported using {{byte[], int}} vs
{{PositionedByteRange}}. The former will be a little slower because of the
extra traversal and pushes that much more into user code, but the features are
identical. That's why I suggest the APIs could be extended later to support
{{PositionedByteRange}} if we can't get consensus today.
[~mcorgan], [~giacomotaylor], [~nkeywal], [~enis]: you've all expressed
opinions about these API. Do these two classes look reasonable to you?
> Update ByteRange to maintain consumer's position
> ------------------------------------------------
>
> Key: HBASE-9091
> URL: https://issues.apache.org/jira/browse/HBASE-9091
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Attachments: 0001-HBASE-9091-Extend-ByteRange.patch,
> 0001-HBASE-9091-Extend-ByteRange.patch,
> 0001-HBASE-9091-Introduce-PositionedByteRange.patch
>
>
> ByteRange is a useful alternative to Java's ByteBuffer. Notably, it is
> mutable and an instance can be assigned over a byte[] after instantiation.
> This is valuable as a performance consideration when working with byte[]
> slices in a tight loop. Its current design is such that it is not possible to
> consume a portion of the range while performing activities like decoding an
> object without altering the definition of the range. It should provide a
> position that is independent from the range's offset and length to make
> partial reads easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
