hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aditya Kishore (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-7115) [shell] Provide a way to register custom filters with the Filter Language Parser
Date Wed, 07 Nov 2012 21:50:13 GMT

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

Aditya Kishore updated HBASE-7115:

    Fix Version/s: 0.96.0
           Status: Patch Available  (was: Open)

Submitting patch for trunk.

Please note that there was a mismatch in the java-doc of {{org.apache.hadoop.hbase.filter.ParseFilter.registerFilter(String,
String)}} API where it stated that if an already registered filter is registered again, a
{{IllegalArgumentException}} will be thrown. The code did not enforce this. This patch corrects
the java-doc to reflect the behavior in code (which is appropriate, IMO).

> [shell] Provide a way to register custom filters with the Filter Language Parser
> --------------------------------------------------------------------------------
>                 Key: HBASE-7115
>                 URL: https://issues.apache.org/jira/browse/HBASE-7115
>             Project: HBase
>          Issue Type: Improvement
>          Components: Filters, shell
>    Affects Versions: 0.96.0
>            Reporter: Aditya Kishore
>            Assignee: Aditya Kishore
>             Fix For: 0.96.0
>         Attachments: HBASE-7115_trunk.patch
> HBASE-5428 added this capability to thrift interface but the configuration parameter
name is "thrift" specific.
> This patch introduces a more generic parameter "hbase.user.filters" using which the user
custom filters can be specified in the configuration and loaded in any client that needs to
use the filter language parser.
> The patch then uses this new parameter to register any user specified filters while invoking
the HBase shell.

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

View raw message