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

Steve Rowe updated LUCENE-4723:
-------------------------------

    Attachment: LUCENE-4723.patch

bq. maybe we can put the foldToASCII.txt just in the tests folder and not with 
the alg files in conf? do we really need it or maybe we can use something 
smaller?

I agree - I've switched to a trimmed down version of 
mapping-ISOLatin1Accent.txt and put it in the tests folder.

I had to make TestPerfTasksLogic copy it from there to the work dir, then tell 
AnalyzerFactoryTask to use work.dir as the base dir for the 
FilesystemResourceLoader passed to each analysis pipeline component factory on 
inform().  I think this should be a fairly general way to allow people pass in 
paths to resources: "put them in the work.dir".

I think it's ready to go.
                
> Add AnalyzerFactoryTask to benchmark, and enable analyzer creation via the 
> resulting factories using NewAnalyzerTask
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-4723
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4723
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/benchmark
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Minor
>         Attachments: LUCENE-4723.patch, LUCENE-4723.patch
>
>
> Benchmark algorithms can't currently use analysis factories.  Instead, one 
> must rely on pre-existing analyzers, or write specialized tasks to construct 
> them.
> Now that all analysis components have factories, benchmark algorithms should 
> be able to use them.

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to