[
https://issues.apache.org/jira/browse/BLUR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546501#comment-13546501
]
Aaron McCurry commented on BLUR-49:
-----------------------------------
Yeah we need a way to initialize analyzers, and I think that Thrift is going to
be tough to make a generic solution. I have a couple of ideas to date, would
love to hear any others.
1. Pass in a javascript function to initialize the analyzers, since this code
is only called when the table is opened or during server restart it doesn't
have to be high performance.
2. Create an abstract initializer class that can except the arguments and
instantiate the new analyzer. This would force use to create some defaults for
each of the standard analyzers, but we would also have to allow users to easily
provide their own classes.
At this point I like the first option better, but I really would like to hear
other people's opinions.
> BlurAnalyzer add constructor arguments
> --------------------------------------
>
> Key: BLUR-49
> URL: https://issues.apache.org/jira/browse/BLUR-49
> Project: Apache Blur
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Aaron McCurry
> Fix For: 0.2.0
>
>
> In the 0.2-dev branch, the BlurAnalyzer should be enhanced to allow
> constructor arguments to be passed in the ClassDefinition.arguments map. Not
> sure what the best way to implement this, but the use case would be creating
> a StandardAnalyzer with a non-default set of stop words.
--
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
