[
https://issues.apache.org/jira/browse/HBASE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081395#comment-13081395
]
stack commented on HBASE-4176:
------------------------------
@Anirudh: Does this patch depend on hbase-1744 going in first? Should we make
that happen first? Meantime here are some comments on what you have posted here.
In future, date, add author to docs, and in this case I'd cite the JIRA it
addresses -- no biggie, just for next time.
This doc looks great. We should be able to add it to the hbase documentation
and include it in a chapter on thrift as a subsection on filters.
Specifying a filter, do I have to give full package name too? (Same for
comparators?) It looks like I do not need too... but maybe it should be
possible?
Doing the compound filters, nested parens will be interpreted properly? (nvm...
in your example I see they do)
Great examples.
Your doc is excellent.
> Exposing HBase Filters to the Thrift API
> ----------------------------------------
>
> Key: HBASE-4176
> URL: https://issues.apache.org/jira/browse/HBASE-4176
> Project: HBase
> Issue Type: Improvement
> Components: thrift
> Reporter: Anirudh Todi
> Assignee: Anirudh Todi
> Priority: Minor
> Attachments: Filter Language.docx, HBASE-4176.patch
>
>
> Currently, to use any of the filters, one has to explicitly add a scanner for
> the filter in the Thrift API making it messy and long. With this patch, I am
> trying to add support for all the filters in a clean way. The user specifies
> a filter via a string. The string is parsed on the server to construct the
> filter. More information can be found in the attached document named Filter
> Language
> This patch is trying to extend and further the progress made by the patches
> in the HBASE-1744 JIRA (https://issues.apache.org/jira/browse/HBASE-1744)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
