[
https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260708#comment-13260708
]
Christopher Currens commented on LUCENENET-486:
-----------------------------------------------
I think this affects other languages more than it does English, well, at least
it affects the German analyzer, since it does umlaut conversions. While I
don't think design change to Lucene.NET is necessary, it might be beneficial to
expose the logic that converts umlauts in terms, so that developers can
manually sanitize the terms in the query themselves (even overriding methods in
QueryParser) so they can get the same behavior. I think that might be a
reasonable compromise, and only affects the GermanAnalyzer in Contrib.
> Wildcard queries are not analyzed
> ---------------------------------
>
> Key: LUCENENET-486
> URL: https://issues.apache.org/jira/browse/LUCENENET-486
> Project: Lucene.Net
> Issue Type: Bug
> Components: Lucene.Net Contrib, Lucene.Net Core
> Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4
> Environment: Windows 7, Visual Studio 2010, .net 4.0
> Reporter: Björn
> Attachments: LuceneTest.zip
>
>
> The lucene 'QueryParser' doesn't analyze wildcard querys. The function
> 'GetPrefixQuery'(QueryParser.cs) returns the string without any analyzation.
> I have performed some queries to show the problem. The analyzer is the
> 'Contrib.Analyzers.DE.GermanAnalyzer'
> ---------- indexed word: 'Häuser'; in the index stemmed as: 'hau' ----------
> query: Hau*; hit: yes
> query: Hause*; hit: no; This should be a hit.....
> ---------- indexed word: 'Angebote'; in the index stemmed as: 'angebo'
> ----------
> query: Angebo*; hit: yes
> query: Angebot*; hit: no; This should be a hit.....
> query: Angebote*; hit: no; This should be a hit.....
> ---------- indexed word: 'Björn'; in the index stemmed as: 'bjor' ----------
> query: Bjor*; hit: yes
> query: Björ*; hit: no; This should be a hit.....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
