hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Gray (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3245) client.Result uses inverted Comparator<Long> in the versionMap (containted in familyMap)
Date Thu, 18 Nov 2010 19:40:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Gray resolved HBASE-3245.
----------------------------------

    Resolution: Not A Problem

Hi Ivan.

This is actually the correct behavior.  In HBase, we sort rows and columns in ascending, lexicographical
order.  However, versions are sorted in descending order (most recent version appears first).

If I'm somehow not understanding the issue, please do re-open the JIRA and provide more explanation.
 Thanks!

> client.Result uses inverted Comparator<Long> in the versionMap (containted in familyMap)
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-3245
>                 URL: https://issues.apache.org/jira/browse/HBASE-3245
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ivan Valchev
>             Fix For: 0.89.20100924
>
>
> In getMap() method the comparator passed to versionMap does:
>       public int compare(Long l1, Long l2) {
>             return l2.compareTo(l1);
>        }
> which inverts the result of the comparison. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message