Wojtek, yes, that's how you can loop through all docs in the index. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ---- From: Wojtek H <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Sunday, April 13, 2008 1:38:35 PM Subject: Re: Document ids in Lucene index Thank you for the answer. So it means that I can without any problems iterate over index documents using this algoritm (I don't want to use MatchAllQuery): - check maxDoc() - iterate from 0 to maxDoc() and process doc if it is not deleted Am I right? Best, wojtek 2008/4/12, Chris Hostetter <[EMAIL PROTECTED]>: > > : I am wondering if there are possible "holes" in set of index documents > > : ids. Being more specific - is it possible that there exist integer i > : between 0 and IndexReader.maxDoc() such that > : reader.document(i) == null > : and > : reader.isDeleted(i)==false > > : ??? > > That should not ever happen ... if it does, I would consider it a bug > until someone smarter then me explained why it isn't. > > (minor nit: document(i) won't ever return null, if you call it on a > deleted docId you'll get an IllegalArgumentException) > > > -Hoss > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
