RE: a proof that every word is indexing properly

2010-12-01 Thread David Fertig
Stop words are never indexed; you may need to empty your stop list. Luke (open-source w/code available) can browse and re-create documents in indexes using their terms already. Compare that to the original to see if you are satisfied. -Original Message- From: David Linde [mailto:davidli

RE: best practice: 1.4 billions documents

2010-11-22 Thread David Fertig
hings like warming searchers, indexing additional documents, or filling FieldCache in parallel. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: David Fertig [mailto:dfer...@cymfony.com] >

RE: best practice: 1.4 billions documents

2010-11-22 Thread David Fertig
much the answer I was searching for: lucene alone is able to manage such a big index. which kind of problems do you have with the parallel searchers? I'm going to build my index in the next couple of weeks if you want we can confront our data thanks again Luca On Sun, Nov 21, 2010 at 6

RE: best practice: 1.4 billions documents

2010-11-21 Thread David Fertig
Actually I've been bitten by an still-unresolved issue with the parallel searchers and recommend a MultiReader instead. We have a couple billion docs in our archives as well. Breaking them up by day worked well for us, but you'll need to do something. -Original Message- From: Luca Ronda

RE: Search returning documents matching a NOT range

2010-11-17 Thread David Fertig
I noticed there is still no JIRA ticket for this, do we have any type on consensus on how this issue will/will not be resolved? If MultiSearcher and and MultiReader do not give the same results, I would think one would be considered "broken" and/or possibly "unfixable". Is MultiSearcher goin

RE: Antw.: Search returning documents matching a NOT range

2010-11-08 Thread David Fertig
s Policeman >> Bremen, Germany >> >> - Reply message ----- >> Von: "Ian Lea" >> Datum: Mo., Nov. 8, 2010 12:45 >> Betreff: Search returning documents matching a NOT range >> An: >> Cc: "David Fertig" >> >> >&

RE: Search returning documents matching a NOT range

2010-11-07 Thread David Fertig
27;re getting what's in the index (and thus being searched) rather than wha's stored in the document. Luke might get you there faster/easier Best Erick On Fri, Nov 5, 2010 at 5:18 PM, David Fertig wrote: > Ian, > Thank you for getting back to me. No, I do not get a bogus

RE: Search returning documents matching a NOT range

2010-11-05 Thread David Fertig
OT range Do you get the bogus hit on the small index if search that index alone? Are you positive it only holds the one doc? Loading the one doc into a new RAM based index in the test would prove it. You are more likely to get help if post a self-contained example - people can see everything rel

RE: RangeQuery with multiple ranges ?

2010-11-05 Thread David Fertig
You can use a query parser to parse your text query into the appropriate query objects. -Original Message- From: Alain Camus [mailto:a...@ngi.be] Sent: Friday, November 5, 2010 11:26 AM To: java-user@lucene.apache.org Subject: RangeQuery with multiple ranges ? Hello list, I'm new to l

Search returning documents matching a NOT range

2010-11-04 Thread David Fertig
I have an active lucene implementation that has been in place for a couple years and was recently upgraded to the 3.02 branch. We are now occasionally seeing documents returned from searches that should not be returned. I have reduced the code and indexes to the smallest set possible where I can st

MergePolicy$MergeException during IndexWriter.addIndexesNoOptimize

2009-02-02 Thread David Fertig
Hello. Hopefully this is the correct forum. I am currently using release 2.3.2 as my stable release, but have tried this 2.4 as well. I have 4 threads indexing documents into separate indexes and then merging them into a larger master index. If the master index is previously corrupted (suc