incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-49) BlurAnalyzer add constructor arguments
Date Fri, 15 Feb 2013 02:53:12 GMT

    [ https://issues.apache.org/jira/browse/BLUR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578916#comment-13578916
] 

Aaron McCurry commented on BLUR-49:
-----------------------------------

I don't know what do you think?  For a first cut I think that we could go with a hard coded
function name until there's a need for something different.  I will take a look at this patch
as soon as I can.  Sorry for the slow responses lately, I've busier than normal at work.

Aaron
                
> 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
>
>         Attachments: 0001-BLUR-ID-49-Added-Javascript-method-call-to-intialize.patch,
0001-BLUR-ID-49-Blur-Analyzer-Added-constructor-arguments.patch
>
>
> 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

Mime
View raw message