Could you attach your patch to this issue? I dont mind looking at potentially adding the ability for a developer to set a flag that would make it behave as you seek.

But that would be an enhancement - as this is now, its intended behavior
Sent from my Windows Phone
________________________________
From: Digy (Commented) (JIRA)
Sent: 4/19/2012 1:45 PM
To: [EMAIL PROTECTED]
Subject: [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-tabpanel&focusedCommentId=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

Hello,

unfortunaly I can't add a file to this closed issue. I have uploaded my
workaround here: http://pastebin.com/B1n5wJds (Diff of function
'GetPrefixQuery'). I'm not very familiar with the lucene code. So I only
invoke 'GetFieldQuery' to analyze the string. Maybe there is a better
solution. But it works for my purpose.

Thank You
Björn

Am 20.04.2012 01:42, schrieb Prescott Nasser:
> Could you attach your patch to this issue? I dont mind looking at potentially adding the ability for a developer to set a flag that would make it behave as you seek.
>
> But that would be an enhancement - as this is now, its intended behavior
>
>
> Sent from my Windows Phone
> ________________________________
> From: Digy (Commented) (JIRA)
> Sent: 4/19/2012 1:45 PM
> To: [EMAIL PROTECTED]
> Subject: [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-tabpanel&focusedCommentId=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
>
>
>