lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Currens <>
Subject Re: Wildcard queries are not analyzed
Date Tue, 17 Apr 2012 18:40:42 GMT
I should also add, that directly reading the token stream, will produce
"bjor" (no wildcard) from "björ*".


It would be great to see some example code that you're using to reproduce
this behavior, just to make sure we're testing it in the same way.  Also,
could I persuade you to create an issue for this here:, so that we can keep track
of the progress on it?


On Tue, Apr 17, 2012 at 11:34 AM, Christopher Currens <> wrote:

> Thanks Björn.
> So I've compared the code with the java equivalent, and the result from
> java, via running the analyzer in the QueryParser:
> Field:björ*
> So, it seems to have the same behavior in Java as well.  I want to see if
> this is a known issue or expected behavior in java, and go from there.  If
> it is, can anyone think of any unexpected side effects to fixing this, so
> "björ*" becomes "bjor*"?
> Thanks,
> Christopher
> 2012/4/17 Björn Kremer <>
>> Hello,
>> maybe I have found a little lucene problem: Wildcard queries are not
>> analyzed correctly. I'm using the german analyzer with the
>> 'GermanDIN2Stemmer'.
>> In the lucene-index my name('Björn') is stored as 'bjorn'. If I performe
>> a wildcard query like 'björ*' the function 'GetPrefixQuery' does not
>> analyze the search term. So the query result is 'björ*' instead of 'bjor*'.
>> (björ* = no match, bjor* = match)
>> Thank You
>> Björn

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message