[ 
https://issues.apache.org/jira/browse/HBASE-18160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-18160:
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.0.0-alpha-3)
                       (was: 1.3.2)
                       (was: 1.2.6)
                       (was: 1.4.0)
                   HBASE-18410
           Status: Resolved  (was: Patch Available)

Currently fixed in the feature branch for HBASE-18410. If you'd like this 
included in other release lines prior to us getting that branch merged back in 
(and potentially backported to earlier versions) feel free to rebase onto 
current master so long as the test from HBASE-18957  doesn't regress.

> Fix incorrect  logic in FilterList.filterKeyValue
> -------------------------------------------------
>
>                 Key: HBASE-18160
>                 URL: https://issues.apache.org/jira/browse/HBASE-18160
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Filters
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>             Fix For: HBASE-18410
>
>         Attachments: HBASE-18160.branch-1.3.v1.patch, 
> HBASE-18160.branch-1.3.v1.patch, HBASE-18160.branch-1.4.v1.patch, 
> HBASE-18160.branch-1.4.v1.patch, HBASE-18160.v1.patch, HBASE-18160.v2.patch, 
> HBASE-18160.v2.patch, HBASE-18160.v3.patch, HBASE-18160.v4.patch, 
> HBASE-18160.v5.patch, HBASE-18160.v6.patch, HBASE-18160.v6.patch, 
> HBASE-18160.v7.patch, HBASE-18160.v8.patch, filter-and-map.txt, 
> filter-or-map.txt
>
>
> As HBASE-17678 said, there are two problems in FilterList.filterKeyValue 
> implementation: 
> 1.  FilterList did not consider INCLUDE_AND_SEEK_NEXT_ROW case( seems like 
> INCLUDE_AND_SEEK_NEXT_ROW is a newly added case, and the dev forgot to 
> consider FilterList), So if a user use INCLUDE_AND_SEEK_NEXT_ROW in his own 
> Filter and wrapped by a FilterList,  it'll  throw  an 
> IllegalStateException("Received code is not valid."). 
> 2.  For FilterList with MUST_PASS_ONE,   if filter-A in filter list return  
> INCLUDE and filter-B in filter list return INCLUDE_AND_NEXT_COL,   the 
> FilterList will return  INCLUDE_AND_NEXT_COL finally.  According to the 
> mininal step rule , It's incorrect.  (filter list with MUST_PASS_ONE choose 
> the mininal step among filters in filter list. Let's call it: The Mininal 
> Step Rule).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to