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

Matt Corgan commented on HBASE-9091:
------------------------------------

Nice going.  I think this will let us do some cool stuff at a higher level of 
abstraction than all the Bytes.java calls.

Do you think it's worth splitting the mutating methods into a sub-interface?  
This would provide helpful guarantees all over the place that users of the 
read-only ByteRange interface aren't modifying anything.  My last opinion 
here... this could go on forever.  Ignore if it can be done later.
                
> 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-Abstract-ByteRange-introduce-PositionedBy.patch, 
> 0001-HBASE-9091-Abstract-ByteRange-introduce-PositionedBy.patch, 
> 0001-HBASE-9091-Extend-ByteRange.patch, 
> 0001-HBASE-9091-Extend-ByteRange.patch, 
> 0001-HBASE-9091-Introduce-PositionedByteRange.patch, 
> 0001-HBASE-9091-Introduce-PositionedByteRange.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

Reply via email to