[
https://issues.apache.org/jira/browse/HBASE-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752792#comment-13752792
]
Wouter Bolsterlee commented on HBASE-7826:
------------------------------------------
Is it really safe to convert a previously required field to an optional one?
Parsers using the old definition file might unconditionally expect the field
when handling input generated using the newer definitions.
> Improve Hbase Thrift v1 to return results in sorted order
> ---------------------------------------------------------
>
> Key: HBASE-7826
> URL: https://issues.apache.org/jira/browse/HBASE-7826
> Project: HBase
> Issue Type: New Feature
> Components: Thrift
> Affects Versions: 0.94.0
> Reporter: Shivendra Pratap Singh
> Assignee: Shivendra Pratap Singh
> Priority: Minor
> Labels: Hbase, Thrift
> Fix For: 0.98.0, 0.95.2, 0.94.11
>
> Attachments: 7826-v6.patch, HBASE-7826-0.94-v7.patch,
> hbase_7826.patch, hbase_7826.patch, HBASE-7826.patch,
> hbase_7826_sortcolumnFlag.1.patch, hbase_7826_sortcolumnFlag.2.patch,
> hbase_7826_sortcolumnFlag.3.patch, hbase_7826_sortcolumnFlag.4.patch,
> hbase_7826_sortcolumnFlag.5.patch, hbase_7826_sortcolumnFlag.patch,
> hbase_7826_trunk.patch
>
>
> Hbase natively stores columns sorted based on the column qualifier. A scan is
> guaranteed to return sorted columns. The Java API works fine but the Thrift
> API is broken. Hbase uses TreeMap that ensures that sort order is maintained.
> However Hbase thrift specification uses a simple Map to store the data. A
> map, since it is unordered doesn't result in columns being returned in a sort
> order that is consistent with their storage in Hbase.
--
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
