[
https://issues.apache.org/jira/browse/LUCENENET-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522927
]
George Aroush commented on LUCENENET-51:
----------------------------------------
Hi DIGY,
I did not encounter this problem to know much about it to give you a
constructive answer. As you must have noticed by now, I care a lot about
keeping the code consistent with the Java version and I believe we all need to
aim for this.
This said, I would like to know what the Java Lucene community has to say about
this issue. At least, I would like to know if this is an issue with the user
code or Lucene code itself. I'm going to post this question on the Java Lucene
mailing list for some input.
Erik: Maybe you already know about this issue, can you comment? Thanks.
Regards,
-- George
> QueryParser.GetPrefixQuery does not use the analyzer
> ----------------------------------------------------
>
> Key: LUCENENET-51
> URL: https://issues.apache.org/jira/browse/LUCENENET-51
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Digy
> Priority: Minor
> Attachments: BugSample.cs, BugSample2.cs, QueryParser.patch
>
>
> Hi all,
> Some custom analyzers use their own LowerCase filters and Stem filters.
> For ex. ÖöÜü is converted by lowercase the filter to oouu(only latin charset)
> and this token is stored in the index.
> But QueryParsers's GetPrefixQuery method does not use the analyzer's
> lowercase filter. So it convert the token to
> lowercase(which is ööüü) and a search like ÖöÜü* returns no result since
> Lucene searches tokens starting with ööüü
> (not with oouu) in the index.
> The same is also valid for stem filters. Assume that a pseudo language's stem
> filter converts the trailing "abcd" to e.
> Then a search like 1234abcd* will return no result even if a token 1234e is
> stored in the index.
> Therefore QueryParsers.GetPrefixQuery method has to be fixed to force to use
> the analyzer.
> GetWildcardQuery, GetFuzzyQuery may also suffer from the same problem.
> I will attach a sample code to show the bug and a patch for GetPrefixQuery
> DIGY.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
