[ https://issues.apache.org/jira/browse/HBASE-13122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343269#comment-14343269 ]
Shuaifeng Zhou commented on HBASE-13122: ---------------------------------------- We have done a performance test, here are the result: FamilyFilter: test table have two familys , each have 3 qualifier, and put 10000 rows into the table, each row&qualifier have 1000 versions. scan use familyFilter get values from the second family, scaned 2000 rows and 100 versions of each row& qualifier. Use the oraginal FamilyFilter, cost average 309 seconds, but with the improved familyFilter, the cost is average 38 seconds, improved about 700% ColumnRangeFilter: The same data but only one family, scan 10000 rows and 1000 versions, orangial cost average 68s, the improved cost 64s, improved a little. Because in the FamilyFilter, the improve will reduce read files, so improved significantly, but the columnRangeFilter can not reduce read files, so imporve little. > Improve efficiency for return codes of some filters > --------------------------------------------------- > > Key: HBASE-13122 > URL: https://issues.apache.org/jira/browse/HBASE-13122 > Project: HBase > Issue Type: Improvement > Components: Filters > Affects Versions: 0.94.24, 1.0.1, 0.98.10.1 > Reporter: Shuaifeng Zhou > Attachments: 13122-master.patch, 13122.patch > > > ColumnRangeFilter: > when minColumnInclusive is false, it means all the cells at the current > row&column not fit the condition, so it should skip to next column, return > code should be NEXT_COL, not SKIP. > FamilyFilter is the similar sitution. > Currently, SKIP will not causing error, but not efficent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)