[
https://issues.apache.org/jira/browse/LUCENENET-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519248
]
George Aroush commented on LUCENENET-51:
----------------------------------------
Hi Digy,
Before I apply this patch, I like to know if this is a port issue or an
existing issue with the Java version of Lucene too. The reason why I asked
this is because I examined the code fragment around your patch and noticed that
the existing code is identical to the Java code and thus, it is behaving as
expected.
Thanks.
-- 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, 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.
