Re: Duplicates results when using a non optimized index

2008-05-15 Thread Mike Klaas
On 15-May-08, at 12:50 AM, Tim Mahy wrote: Hi, yep it is a very strange problem that we never encountered before. We are uploading all the documents again to see if that solves the problem (hoping that the delete will delete also the multiple document instances) If you are re-adding ever

RE: Duplicates results when using a non optimized index

2008-05-15 Thread Tim Mahy
Gospodnetic [EMAIL PROTECTED] Verzonden: woensdag 14 mei 2008 23:18 Aan: solr-user@lucene.apache.org Onderwerp: Re: Duplicates results when using a non optimized index Tim, Hm, not sure what caused this. 1.2 is now quite old (yes, I know it's the last stable release), so if I were you I would con

Re: Duplicates results when using a non optimized index

2008-05-14 Thread Otis Gospodnetic
--> we use the 1.2 stable build > > greetings, > Tim > > Van: Otis Gospodnetic [EMAIL PROTECTED] > Verzonden: woensdag 14 mei 2008 6:11 > Aan: solr-user@lucene.apache.org > Onderwerp: Re: Duplicates results when using a non optimized ind

RE: Duplicates results when using a non optimized index

2008-05-14 Thread Tim Mahy
6:11 Aan: solr-user@lucene.apache.org Onderwerp: Re: Duplicates results when using a non optimized index Hm, not sure why that is happening, but here is some info regarding other stuff from your email - there should be no duplicates even if you are searching an index that is being optimized - why a

Re: Duplicates results when using a non optimized index

2008-05-13 Thread Otis Gospodnetic
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Tim Mahy <[EMAIL PROTECTED]> > To: "solr-user@lucene.apache.org" > Sent: Tuesday, May 13, 2008 5:59:28 AM > Subject: Duplicates results when using a non optimized index &

Duplicates results when using a non optimized index

2008-05-13 Thread Tim Mahy
Hi all, is this expected behavior when having an index like this : numDocs : 9479963 maxDoc : 12622942 readerImpl : MultiReader which is in the process of optimizing that when we search through the index we get this : 15257559 15257559 17177888 11825631 11825631 The id field is decl