You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jieshan Bean (JIRA)" <ji...@apache.org> on 2012/05/07 14:38:56 UTC

[jira] [Created] (HBASE-5950) Add a decimal comparator for Filter

Jieshan Bean created HBASE-5950:
-----------------------------------

             Summary: 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.96.0
            Reporter: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-5950) Add a decimal comparator for Filter

Posted by "Jieshan Bean (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461734#comment-13461734 ] 

Jieshan Bean commented on HBASE-5950:
-------------------------------------

This comparator is not needed if we store the Integer/Double/Float as bytes directly. Right?
                
> 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.96.0
>            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 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

[jira] [Assigned] (HBASE-5950) Add a decimal comparator for Filter

Posted by "Jieshan Bean (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jieshan Bean reassigned HBASE-5950:
-----------------------------------

    Assignee: Jieshan Bean
    
> 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.96.0
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-5950) Add a decimal comparator for Filter

Posted by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461731#comment-13461731 ] 

ramkrishna.s.vasudevan commented on HBASE-5950:
-----------------------------------------------

Infact for comparing the negative and positive numbers we need a similar comparator.
Otherwise Binary Comparator will represent -6 to be greater than -5.
                
> 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.96.0
>            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 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