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

Hudson commented on HBASE-16310:
--------------------------------

FAILURE: Integrated in HBase-Trunk_matrix #1389 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1389/])
HBASE-16310 Revisit the logic of filterRowKey for Filters (Ram) (ramkrishna: 
rev 2d203e6053defb52cd3629d49ae6d54460c658dd)
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/filter/PrefixFilter.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/filter/PageFilter.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultiRowRangeFilter.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/filter/InclusiveStopFilter.java


> Revisit the logic of filterRowKey for Filters
> ---------------------------------------------
>
>                 Key: HBASE-16310
>                 URL: https://issues.apache.org/jira/browse/HBASE-16310
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 1.1.5, 1.2.2
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16310.patch, HBASE-16310_1.patch, 
> HBASE-16310_1.patch, HBASE-16310_1.patch, HBASE-16310_2.patch
>
>
> Based on HBASE-16926 it was observed that filterRowKey() API behaviour for 
> FilterList and a standalone filter should be made consistent. This JIRA is to 
> track down the changes and ensure 1.3+ on wards we have consistent behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to