Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Message-ID: <4050BD70.7080804@newsmonster.org>
Date: Thu, 11 Mar 2004 11:26:40 -0800
From: "Kevin A. Burton" <burton@newsmonster.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Lucene Users List <lucene-user@jakarta.apache.org>
Subject: Re: update performance
References: <4050A36D.4080209@seeqa.com> <4050A8D4.10900@apache.org>
 <4050B012.7040104@seeqa.com>
In-Reply-To: <4050B012.7040104@seeqa.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigDF51B07BE586B9952448E59C"

--------------enigDF51B07BE586B9952448E59C
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chris Kimm wrote:

> Unfortunately, I'm not able to batch the updates.  The application 
> needs to make some descisions based on what each document looks like 
> before and  after the update, so I have to do it one at a time.  I 
> guess this is not a common useage scenario for Lucene.  Otherwise, an 
> update() might already be built in somewhere.
>
> Is there anything in the locking/sync framework which precludes saving 
> the cost of closing the Directory object and deleting the temp lock 
> file each time an update is made?
>
Use a RAM directory... then when you're pretty sure you're done call 
IndexWriter.addIndexes() on the disk index.

Will that work for you?

You can also do this every N documents, or minutes, or memory usage, and 
have the commit work with a synchronized thread.

Kevin

-- 

Please reply using PGP.

    http://peerfear.org/pubkey.asc    
    
    NewsMonster - http://www.newsmonster.org/
    
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
       AIM/YIM - sfburtonator,  Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
  IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster


--------------enigDF51B07BE586B9952448E59C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAUL1w6E2NBJnxRBIRAh5GAJwISw56IY51S0wA/DS2UvwIowbDUQCdEnNH
b2KpN7mn5iC+3DKQtI5ssVs=
=Iv8i
-----END PGP SIGNATURE-----

--------------enigDF51B07BE586B9952448E59C--