Re: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior

2011-07-19 Thread Thomas Rewig
ttp://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Thomas Rewig [mailto:tre...@mufin.com] Sent: Monday, July 18, 2011 12:06 PM To: java-user@lucene.apache.org Subject: Re: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior Hi Ian, yes the sc

RE: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior

2011-07-18 Thread Uwe Schindler
nal Message- > From: Thomas Rewig [mailto:tre...@mufin.com] > Sent: Monday, July 18, 2011 12:06 PM > To: java-user@lucene.apache.org > Subject: Re: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special > character behavior > > Hi Ian, > > yes the score is ident

Re: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior

2011-07-18 Thread Thomas Rewig
Hi Ian, yes the score is identical but the inner ordering of same scores seems to be different in the versions. In Lucene 3.3.0 it seems that terms with special characters will be preferred before the exact hit. My code is: PhraseQuery query = new PhraseQuery(); query.add(new

Re: TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior

2011-07-18 Thread Ian Lea
I'm not sure what you are getting at. A search using 3.1.0 and 3.3.0 returns the same docs with identical scores, except that one gives them in order A,B and the other in order B,A? What search method are you using? Does it guarantee anything about the order of returning docs with identical scor

TermQuery - ExactMatching, Lucene 3.1.0 vs. 3.3.0, special character behavior

2011-07-15 Thread Thomas Rewig
Hello, there is a index with a lot of docs, 2 of them are: doc1: 1.Field=idITSVopfOLB=ITS---f0-- Value= 192 2.Field=name ITSVopfOLB=ITS0-- Value= queen doc2: 1.Field=idITSVopfOLB=ITS---f0-- Value= 701492 2.Field=name ITSVopfOLB=ITS0-- V