You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Aditya Kishore (JIRA)" <ji...@apache.org> on 2012/11/07 22:20:12 UTC
[jira] [Created] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Aditya Kishore created HBASE-7115:
-------------------------------------
Summary: [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
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
[jira] [Commented] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493516#comment-13493516 ]
Aditya Kishore commented on HBASE-7115:
---------------------------------------
[~stack] Have updated the JIRA description.
> [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 defined 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.
> Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
> To do that, I would add the following configuration to {{hbase-site.xml}}
> {panel}{{<property>}}
> {{ <name>hbase.user.filters</name>}}
> {{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
> {{</property>}}{panel}
> Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
> {code}
> hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
> ROW COLUMN+CELL
> status column=cf:a, timestamp=304385520000, value=world_peace
> 1 row(s) in 0.0000 seconds
> {code}
--
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
[jira] [Commented] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492781#comment-13492781 ]
Hadoop QA commented on HBASE-7115:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12552545/HBASE-7115_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 87 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 15 new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3259//console
This message is automatically generated.
> [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
[jira] [Commented] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493013#comment-13493013 ]
stack commented on HBASE-7115:
------------------------------
[~adityakishore] Patch looks good. Can you drop in here a session that shows your new functionality in action Aditya just so we see it works. Filters still have to be in client and server classpaths, right?
> [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
[jira] [Updated] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditya Kishore updated HBASE-7115:
----------------------------------
Description:
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 defined 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.
Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
To do that, I would add the following configuration to {{hbase-site.xml}}
{panel}{{<property>}}
{{ <name>hbase.user.filters</name>}}
{{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
{{</property>}}{panel}
Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
{code}
hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
ROW COLUMN+CELL
status column=cf:a, timestamp=304385520000, value=world_peace
1 row(s) in 0.0000 seconds
{code}
was:
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.
> [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 defined 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.
> Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
> To do that, I would add the following configuration to {{hbase-site.xml}}
> {panel}{{<property>}}
> {{ <name>hbase.user.filters</name>}}
> {{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
> {{</property>}}{panel}
> Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
> {code}
> hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
> ROW COLUMN+CELL
> status column=cf:a, timestamp=304385520000, value=world_peace
> 1 row(s) in 0.0000 seconds
> {code}
--
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
[jira] [Updated] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditya Kishore updated HBASE-7115:
----------------------------------
Attachment: HBASE-7115_trunk.patch
> [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
> 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
[jira] [Commented] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492808#comment-13492808 ]
Aditya Kishore commented on HBASE-7115:
---------------------------------------
These failures are related to metrics2 changes.
> [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
[jira] [Updated] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditya Kishore updated HBASE-7115:
----------------------------------
Description:
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 defined 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.
Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
To do that, I would add the following configuration to {{hbase-site.xml}}
{panel}{{<property>}}
{{ <name>hbase.user.filters</name>}}
{{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
{{</property>}}{panel}
Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
{code}
hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
ROW COLUMN+CELL
status column=cf:a, timestamp=304385520000, value=world_peace
1 row(s) in 0.0000 seconds
{code}
To use this feature in any client, the client needs to make the following function call as part of its initialization.
{code}
ParseFilter.registerUserFilters(configuration);
{code}
was:
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 defined 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.
Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
To do that, I would add the following configuration to {{hbase-site.xml}}
{panel}{{<property>}}
{{ <name>hbase.user.filters</name>}}
{{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
{{</property>}}{panel}
Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
{code}
hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
ROW COLUMN+CELL
status column=cf:a, timestamp=304385520000, value=world_peace
1 row(s) in 0.0000 seconds
{code}
> [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 defined 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.
> Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
> To do that, I would add the following configuration to {{hbase-site.xml}}
> {panel}{{<property>}}
> {{ <name>hbase.user.filters</name>}}
> {{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
> {{</property>}}{panel}
> Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
> {code}
> hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
> ROW COLUMN+CELL
> status column=cf:a, timestamp=304385520000, value=world_peace
> 1 row(s) in 0.0000 seconds
> {code}
> To use this feature in any client, the client needs to make the following function call as part of its initialization.
> {code}
> ParseFilter.registerUserFilters(configuration);
> {code}
--
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
[jira] [Commented] (HBASE-7115) [shell] Provide a way to register
custom filters with the Filter Language Parser
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493520#comment-13493520 ]
Aditya Kishore commented on HBASE-7115:
---------------------------------------
And yes, this only registers the custom filters with the Filter Language Parser and not does not add the JARS to client/server class path. Let me think about it. Probably we can load the filter jars in the same way co-processors jars are picked.
> [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 defined 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.
> Example usage: Let's say I have written a couple of custom filters with class names *{{org.apache.hadoop.hbase.filter.custom.SuperDuperFilter}}* and *{{org.apache.hadoop.hbase.filter.custom.SilverBulletFilter}}* and I want to use them from HBase shell using the filter language.
> To do that, I would add the following configuration to {{hbase-site.xml}}
> {panel}{{<property>}}
> {{ <name>hbase.user.filters</name>}}
> {{ <value>}}*{{SuperDuperFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SuperDuperFilter,}}*{{SilverBulletFilter}}*{{:org.apache.hadoop.hbase.filter.custom.SilverBulletFilter</value>}}
> {{</property>}}{panel}
> Once this is configured, I can launch HBase shell and use these filters in my {{get}} or {{scan}} just the way I would use a built-in filter.
> {code}
> hbase(main):001:0> scan 't', {FILTER => "SuperDuperFilter(true) AND SilverBulletFilter(42)"}
> ROW COLUMN+CELL
> status column=cf:a, timestamp=304385520000, value=world_peace
> 1 row(s) in 0.0000 seconds
> {code}
--
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