[
https://issues.apache.org/jira/browse/HBASE-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469906#comment-13469906
]
Hudson commented on HBASE-6757:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #8 (See
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/8/])
HBASE-6757 Very inefficient behaviour of scan using FilterList (Revision
1383749)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java
> Very inefficient behaviour of scan using FilterList
> ---------------------------------------------------
>
> Key: HBASE-6757
> URL: https://issues.apache.org/jira/browse/HBASE-6757
> Project: HBase
> Issue Type: Bug
> Components: Filters
> Affects Versions: 0.90.6
> Reporter: Jerry Lam
> Assignee: Lars Hofhansl
> Fix For: 0.94.2, 0.96.0
>
> Attachments: 6757.txt, CopyOfTestColumnPrefixFilter.java,
> DisplayFilter.java
>
>
> The behaviour of scan is very inefficient when using with FilterList.
> The FilterList rewrites the return code from NEXT_ROW to SKIP from a filter
> if Operator.MUST_PASS_ALL is used.
> This happens when using ColumnPrefixFilter. Even though the
> ColumnPrefixFilter indicates to jump to NEXT_ROW because no further match can
> be found, the scan continues to scan all versions of a column in that row and
> all columns of that row because the ReturnCode from ColumnPrefixFilter has
> been rewritten by the FilterList from NEXT_ROW to SKIP.
> This is particularly inefficient when there are many versions in a column
> because the check is performed on all versions of the column instead of just
> by checking the qualifier of the column name.
--
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
