Re: Document ids in Lucene index

2008-04-14 Thread Chris Hostetter
: - check maxDoc() : - iterate from 0 to maxDoc() and process doc if it is not deleted For the record: that is exactly what MatchAllDocsQuery does ... except that you have an off by one error (maxDoc returns 1 more then the largest possible document number). Even if you don't want the Query AP

Re: Document ids in Lucene index

2008-04-13 Thread Otis Gospodnetic
ocument 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

Re: Document ids in Lucene index

2008-04-13 Thread Wojtek H
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 <[EMA

Re: Document ids in Lucene index

2008-04-11 Thread Chris Hostetter
: 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 i

Document ids in Lucene index

2008-04-09 Thread Wojtek H
Hi all, 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 ??? Regards, wojtek --