On Mon, 2009-01-26 at 11:55 +0100, Ian Lea wrote:
> for (int i = 0; i < max; i++) {
> if (!reader.isDeleted(i)) {
> Document doc = reader.document(i);
> ...
> }
Hey! You've stolen our code! :-)
While we don't use Lucene in the same way as you, we also perform
iterations over all doc
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Ian Lea [mailto:ian@gmail.com]
> Sent: Monday, January 26, 2009 11:55 AM
> To: java-user@lucene.apache.org
> Subject: Re: IndexReader.is
OK, interesting. This case looks like it'd be a good fit for
iteration-API to access deleted docs. (And, a good case for column-
stride fields, too!).
Thanks for sharing Ian,
Mike
Ian Lea wrote:
Hi Mike
I've got some applications that use lucene purely as a place to store
data, with
Hi Mike
I've got some applications that use lucene purely as a place to store
data, with no searching other than by product id, and have programs
that get all the data out of the store by code like
for (int i = 0; i < max; i++) {
if (!reader.isDeleted(i)) {
Document doc = reader.docume
OK, interesting, thanks. What do you use the deletedDocs iterator for?
Yes, MatchAllDocsQuery should soon be fixed to not use the
synchronized IndexReader.isDeleted method internally:
https://issues.apache.org/jira/browse/LUCENE-1316
Mike
John Wang wrote:
Mike:
"We are conside
Mike:
"We are considering replacing the current random-access
IndexReader.isDeleted(int docID) method with an iterator & skipTo
(DocIdSet) access that would let you iterate through the deleted
docIDs, instead."
This is exactly what we are doing. We do have to however, build the
intern
