[
https://issues.apache.org/jira/browse/HBASE-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541430#comment-14541430
]
Anoop Sam John commented on HBASE-5950:
---------------------------------------
Yes if the Integer/Double/Float values are stored by converting into its bytes
form, the existing comparator itself can work correctly. All values to have the
same type. You can not have one value int 101 converted to its bytes form and
another 100.1 converted to its bytes form. The comparator will give wrong
results. 101 should be converted to bytes form of 101.0
So do we really need new comparator ?
> Add a decimal comparator for Filter
> -----------------------------------
>
> Key: HBASE-5950
> URL: https://issues.apache.org/jira/browse/HBASE-5950
> Project: HBase
> Issue Type: New Feature
> Components: Filters
> Affects Versions: 0.94.0, 0.95.2
> Reporter: Jieshan Bean
> Assignee: Jieshan Bean
>
> Suppose we have a requirement like below:
> we want to get the rows with one specified column value larger than A and
> less than B.
> (They are all decimals or integers)
> namely:
> A < Integer.valueof(column) < B
> Use BinaryComparator will not help us to archive that goal:
> e.g. suppose A = 100, B = 200, one column value is 110000.
> So it can satisfy that condition, but it's not the row we wanted.
>
> So I suggest to add one comparator to help implementing this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
