hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathaniel Cook (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3335) Add BitComparator for filtering
Date Fri, 17 Dec 2010 17:38:03 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972558#action_12972558

Nathaniel Cook commented on HBASE-3335:

The comparator is working for me in my small development cluster of 4 machines. So I after
looking into the HbaseObjectWritable I agree it needs to be added. I am pretty new to HBase
so why does it work on the small cluster even without being in the HbaseObjectWritable map?
I'll add it and submit a new patch.

> Add BitComparator for filtering
> -------------------------------
>                 Key: HBASE-3335
>                 URL: https://issues.apache.org/jira/browse/HBASE-3335
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Nathaniel Cook
>            Priority: Minor
>         Attachments: HBASE-3335.patch, HBASE-3335.v2.patch
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> There are many uses cases for setting bits flags and being able filter on those seems
like a good idea.
> The BitComparator would take a byte[] and a bitwise operator for its constructor. It
would perform the bitwise operation on the column value bytes with the specified byte[]. Then
return whether the result was non-zero. 
> Only the CompareOp.EQUAL and CompareOp.NOT_EQUAL would make sense with this comparator.
> The binary bitwise operators that apply  are AND, OR, and XOR. 

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

View raw message