hbase-issues mailing list archives

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

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

stack commented on HBASE-3335:

I think HbaseObjectWritable passes Strings if a code can't be found. This facility was broken
for longest time but I believe it may have been fixed recently.  This would be my guess as
to why it worked for you.

> 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, HBASE-3335.v3.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