lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Rewig <>
Subject TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior
Date Fri, 15 Jul 2011 14:01:40 GMT

there is a index with a lot of docs, 2 of them are:


     1.Field=id            ITSVopfOLB=ITS---f0-- Value= 192
     2.Field=name     ITSVopfOLB=ITS----0-- Value= queen


     1.Field=id            ITSVopfOLB=ITS---f0-- Value= 701492
     2.Field=name     ITSVopfOLB=ITS----0-- Value= queen板野友美 (Here 
are chinese characters - hopefully you can see them)

if I search in the index - with a TermQuery there is a different 
behavior between Lucene 3.1.0 and 3.3.0 :


     Term:field='name' text='queen'

Result Lucene 3.1.0:

     0    Score=13,2132    Doc.Id=176002    id=192 name=queen
     1    Score=13,2132    Doc.Id=523407    id=701492 name=queen板野友美

Result Lucene 3.3.0:

     0    Score=13,2132    Doc.Id=523407    id=701492 name=queen板野友美
     1    Score=13,2132    Doc.Id=176002    id=192 name=queen

The result from Lucene 3.1.0 is that, what I would expect if I do a 
'exact matching' Term Query.
Each index was indexed with its associated LuceneVersion.
I tested it with luke and with my own Code - the result was always the 

Is it a new feature in Lucene 3.3.0 or a bug?

Thanks in advance!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message