: The Searching process then would have to re-open it's RAMDirectory.
the key to all of this being that there are constructors for RAMDirectory
that make it very easy to load in the contents of an FSDirectory.
: Or you check the version of the fs-based index from time to time, to see
: when it h
code/design change, I thought I should first find out if there was any way
I could lessen the work.
Venu
-Original Message-
From: Jens Kraemer [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 7:19 PM
To: java-user@lucene.apache.org
Subject: Re: Keeping RAMDirectory and filesystem
On Mon, Mar 13, 2006 at 06:23:10PM +0530, Satuluri, Venu_Madhav wrote:
> Hi,
>
> Is there an elegant way to keep RAMDirectory and my file-system based
> index in sync? I have a java class that is periodically started up by
> crond that checks for modified documents and then reindexes them onto
> t
Hi,
Is there an elegant way to keep RAMDirectory and my file-system based
index in sync? I have a java class that is periodically started up by
crond that checks for modified documents and then reindexes them onto
the filesystem. However, for searching I want to use RAMDirectory (for
the performan
