[
https://issues.apache.org/jira/browse/HBASE-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617722#comment-13617722
]
Jean-Daniel Cryans commented on HBASE-7826:
-------------------------------------------
This cannot go into 0.94 as it is incompatible.
Regarding trunk, I'm worried about using a list since users usually rely on
being able to directly get a cell (like you can do with Result.getColumn in the
Java API) which seems like a more default use case than scanning through the
list of qualifiers. In other words, what are users more likely to do: write
their own code to get a sorted list (current situation) or write their own code
to search the list for particular cells (with this patch)?
My opinion right now is to keep status quo.
> 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
> Attachments: hbase_7826.patch, hbase_7826.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
