[
https://issues.apache.org/jira/browse/HBASE-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428539#comment-13428539
]
Hadoop QA commented on HBASE-6509:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12539130/HBASE-6509_1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 10 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2501//console
This message is automatically generated.
> Implement fast-forwarding FuzzyRowFilter to allow filter rows e.g. by
> "???alex?b"
> ---------------------------------------------------------------------------------
>
> Key: HBASE-6509
> URL: https://issues.apache.org/jira/browse/HBASE-6509
> Project: HBase
> Issue Type: New Feature
> Components: filters
> Reporter: Alex Baranau
> Assignee: Alex Baranau
> Priority: Minor
> Attachments: HBASE-6509.patch, HBASE-6509_1.patch
>
>
> Implement fuzzy row key filter to allow fetching records e.g. by this
> criteria: "???alex?b".
> This seems to be very useful as an alternative to select records by row keys
> by specifying their part which is not prefix part. Due to fast-forwarding
> nature of the filter in many situations this helps to avoid heavy full-table
> scans.
> This is especially effective when you have composite row key and (some of)
> its parts has fixed length. E.g. with the key of format userId_actionId_time,
> given that userId and actionId length is fixed, one can select user actions
> of specific type using fuzzy row key by specifying mask "????_myaction".
> Given fast-forwarding nature of filter, this will usually work much faster
> than doing whole table scan with any of the existing server-side filters.
> In many cases this can work as secondary-indexing alternative.
> Many times users implement it as a custom filter and many times they just
> don' know this is possible. Let's add it to the common codebase.
--
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
