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

Nick Dimiduk commented on HBASE-7692:
-------------------------------------

Please see 
[hbase/7692-ordered-serialization|https://github.com/ndimiduk/hbase/tree/7692-ordered-serialization].
 I've imported the [Orderly|https://github.com/ndimiduk/orderly] library into 
hbase-common and hadoop-examples. In an attempt to break it down into 
reviewable chunks, I've split it over 7 commits. The 1st introduces the base 
classes and support for byte types, the 2nd adds support for String types, the 
3rd for integers, the 4th for longs, the 5th for decimals, and the 6th for 
compound types (or "structs"). The final commit adds additional documentation, 
cleans up spelling mistakes, javadoc warnings, and generally prepares the code 
for HadoopQA.

I'll also attach the monster-diff to this ticket so that HadoopQA can do it's 
thing.
                
> Add utility class to generate ordered byte[] serialization
> ----------------------------------------------------------
>
>                 Key: HBASE-7692
>                 URL: https://issues.apache.org/jira/browse/HBASE-7692
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>         Attachments: HBASE-7692.v1.patch
>
>
> The current Bytes utility class works, but produces output that does not 
> maintain the native sort ordering of the input value. This results in, for 
> example, a negative value that does not necessarily sort before a positive 
> value. HBase should provide a canonical implementation of such a 
> serialization format so that third-parties can reliably build on top of 
> HBase. This will allow an implementation for HIVE-3634, HIVE-2599, or 
> HIVE-2903 that is compatible with similar features in Pig.

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