Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Problem updating index while reader is open
Date: Wed, 23 Aug 2006 13:04:23 +0200
Message-ID: <6F4F5B8F19AA954DB9002305E4D6D14901BD98@ad01.aza.se>
Thread-Topic: Problem updating index while reader is open
Thread-Index: AcbGo8oxewzV3zZCRL2m+y5RPop/1w==
From: =?iso-8859-1?Q?Bj=F6rn_Ekengren?= <bjorn.ekengren@avanza.se>
To: <java-user@lucene.apache.org>

If I try to add documents to an index while a reader is open I get en =
error message saying "Cannot delete C:\myindex\_3n.f0". I suspect that =
this is due to the fact that the windows fs won't allow deletion of a =
file when there is a filehandler connected to it. The solution I have at =
the moment is this:

            boolean isWindows =3D =
System.getProperty("os.name").indexOf("indows")!=3D-1;
            IndexReader reader =3D =
searcher.getIndexSearcher().getIndexReader();
            try {
                if(isWindows)
                    reader.close(); // Need to close reader on windows =
since the windows file system won't allow deletion of a file with an =
open filehandler
                IIndexer indexer =3D searcher.getIndexer();
                addedDocuments =3D indexer.rebuildIndex();
                if(isWindows)
                    searcher.setIndexSearcher(new =
IndexSearcher(searcher.getIndexDir()));//restore index searcher
            } catch (IOException e) {
                e.printStackTrace();
            }

However this means that I cannot search the index while updating it (or =
in this case rebuilding it completely). Are there any workaround for =
this ? Maybe you could rebuild the index into another place on the disk =
and when it is finished set the searcher to operate in the new place. =
This would lead to that it is not possible to query the new index until =
finished. Could you get around this if you build the new index as a =
RamDirectory which is flushed to disk when finished ?

--regards

/Bjorn

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org