[ http://issues.apache.org/jira/browse/LUCENE-101?page=all ]
Daniel Naber closed LUCENE-101.
-------------------------------
Resolution: Fixed
Closing, the code changes the original report talks about don't seem to be
needed anymore today.
> Selecting a language-specific analyzer according to a locale.
> -------------------------------------------------------------
>
> Key: LUCENE-101
> URL: http://issues.apache.org/jira/browse/LUCENE-101
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Analysis
> Affects Versions: unspecified
> Environment: Operating System: other
> Platform: Other
> Reporter: Eric Isakson
> Priority: Minor
>
> Moved from todo.xml:
> Now we rewrite parts of Lucene code in order to use another analyzer. It will
> be useful to select analyzer without touching code.
> This was orginally request by Kazuhiro Kazama ([EMAIL PROTECTED]) in
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=lucene-
> [EMAIL PROTECTED]&msgId=338928
> Not sure if this was completed to Kazuhiro Kazama's satisfaction in the
> current
> CVS. We can certainly choose which analyzer to use for a given IndexWriter
> and
> QueryParser it sounded like he was asking for something like a factory the
> would create an analyzer based on a locale but unless I don't understand
> things
> quite right, searching an index with any analyzer that you didn't create the
> index with is bound to cause you to have false hits in your results.
> Perhaps this is fixed or no action should be taken. Can someone with a better
> understanding of the request comment on this one or close it out?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
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]
