[
https://issues.apache.org/jira/browse/HBASE-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409875#comment-15409875
]
Sean Busbey commented on HBASE-16310:
-------------------------------------
precommit only runs unit tests in the modules that a given patch changes. if
you want test to run in additional modules, you'll have to cause a change
there. an easy way to test project-wide is to include a second commit that
touches the top level pom. Just don't push that second commit at the end.
> 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, 1.3.0
>
> Attachments: HBASE-16310.patch, HBASE-16310_1.patch,
> HBASE-16310_1.patch, HBASE-16310_1.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)
