: 1) Adding 250K documents took half an hour for lucene.
: 2) Deleting and adding same 250K documents took more than 50 minutes. In my
: test all 250K objects are new so there is nothing to delete.
:
: Looks like there is no other way to make it fast.
I bet you can find an improvement in the spec
Hi Praveen,
>
> I tested as follows:
> 1) Adding 250K documents took half an hour for lucene.
> 2) Deleting and adding same 250K documents took more than 50 minutes. In my
> test all 250K objects are new so there is nothing to delete.
>
> Looks like there is no other way to make it fast.
>
Depe
From: "Morus Walter" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Friday, January 14, 2005 8:37 AM
Subject: Re: Best way to find if a document exists, using Reader ...
Praveen Peddi writes:
Does it makes sense to call docFreq or termDocs (which ever is fas
Praveen Peddi writes:
>
> Does it makes sense to call docFreq or termDocs (which ever is faster) before
> calling delete?
>
IMO no.
calling termDocs is what Reader.delete(Term) does:
public final int delete(Term term) throws IOException {
TermDocs docs = termDocs(term);
if (docs == n
Hi luceners,
Using Reader, whats the best (fastest) way to find if a documents exists with a
given term. The term is unique ID, meaning, with that term, atmost one document
can exist.
I have seen 2 appropriate methods of Reader. docFreq(Term) and termDocs(Term).
docFreq should return either 0 o
