[jira] [Created] (LUCENENET-486) Wildcard queries are not analyzed
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.4, Lucene.Net 2.9.2 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
[jira] [Updated] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Björn updated LUCENENET-486: Description: 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. was: 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. 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
[jira] [Closed] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Digy closed LUCENENET-486. -- Resolution: Not A Problem http://wiki.apache.org/lucene-java/LuceneFAQ#Are_Wildcard.2C_Prefix.2C_and_Fuzzy_queries_case_sensitive.3F 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
[jira] [Commented] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257728#comment-13257728 ] Björn commented on LUCENENET-486: - Quote: The reason for skipping the Analyzer is that if you were searching for dogs* you would not want dogs first stemmed to dog, since that would then match dog* This statement is senseless. If I use an analyzer for indexing the word dogs it is stemmed to dog. So a search for dogs* will never be a hit.. 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
[jira] [Commented] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257734#comment-13257734 ] Björn commented on LUCENENET-486: - A supplement for my last comment: The 'StandardAnalyzer' doesn't stem 'dogs' to 'dog'. 'dogs' is indexed as 'dogs'. So this analyzer works correct. The 'GermanAnalyzer' doesn't work correct. 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
[jira] [Reopened] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Björn reopened LUCENENET-486: - 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
[jira] [Closed] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Digy closed LUCENENET-486. -- Resolution: Won't Fix 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
[jira] [Commented] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257791#comment-13257791 ] Björn commented on LUCENENET-486: - Of course I have solved the problem for myself. But this isn't a good behaviour Especially because the FAQ entry is wrong. Not finding a word is a better behaviour than maybe finding too much terms? Ok How can I explain a customer that he can't search a word that he can see in the index? 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
[jira] [Commented] (LUCENENET-486) Wildcard queries are not analyzed
[ https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257792#comment-13257792 ] Digy commented on LUCENENET-486: bq. Of course I have solved the problem for myself. Then no problem DIGY 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
