lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENENET-51) QueryParser.GetPrefixQuery does not use the analyzer
Date Wed, 29 Aug 2007 13:07:30 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523562
] 

Digy commented on LUCENENET-51:
-------------------------------

Thanks Hoss. I see that using analyzer is not suitable for that case, so QueryParser.patch
is invalid for this bug.

Do you know whether it has been discussed before, "adding tostring method to analyzer(s) which,
in turn, uses its lowerCaseFilter(custom or built-in) to convert the token to lowercase".
 [instead of calling string.toString directly, analyzer.toString can be invoked to change
the text to lower-case.]


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


Mime
View raw message