hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clint Morgan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-583) RangeRowFilter, allow to choose rows based on a (lexicographic) comparison to column's values
Date Wed, 21 May 2008 22:41:55 GMT

    [ https://issues.apache.org/jira/browse/HBASE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598834#action_12598834
] 

Clint Morgan commented on HBASE-583:
------------------------------------

This filter is used to filter based on the value of a given column. It takes an operator (equal,
greater, not equal, etc) and either a byte [] value or a byte [] comparator. If we have a
byte [] value then we just do a lexicographic compare. If this is not sufficient (eg you want
to deserialize a long and then compare it to a fixed long value, then you can pass in your
own comparator instead.

This is more powerful than RegexpRowFilter which just does equals comparisons on the columns
because we can do no lexicographic comparisons, and operators other than equals.

I would suggest deprecating the functionality (setColumnFilter and the constructor that takes
columnFilter) from RegexpRowFilter as well. (This functionality should not even be in there
if you believe its name)

Speaking of names, maybe this is not the best name. How about ColumnValueFilter?

> RangeRowFilter, allow to choose rows based on a (lexicographic) comparison to  column's
values
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-583
>                 URL: https://issues.apache.org/jira/browse/HBASE-583
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: filters
>            Reporter: Clint Morgan
>            Assignee: Clint Morgan
>            Priority: Minor
>         Attachments: hbase-583-v2.patch, hbase-583-v3.patch, hbase-583.patch
>
>
> This allows one to do equal, greater than, etc comparisons on column values. Only rows
with columns which pass comparison get through.
> Its cleaner and more powerful than the "columnFilter" in RegExpRowFilter which only provides
equals. I think this functionality should be deprecated in RegExpRowFilter.

-- 
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