Mailing List Archive: Transactional Indexing

I have noticed that when I kill/interrupt an indexing process, that it
leaves a "lock" file, preventing further indexing.

This raises a couple of questions:
a. When I simply delete the file and restart the indexing, it seems to work.
Is there a risk in doing this?

b. Can indexing be done in a concurrent fashion? For example, allowing
multiple uploading of files over the web and doing incremental indexing as
they arrive. In this situation, you may have several documents that need to
be indexed simultaneously.

Also I have seen some mention of a mailing list archive... how does one find
it or search it? I do not see a reference at apache.org.

Thanks

--
To unsubscribe, e-mail: <mailto:lucene-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-user-help@jakarta.apache.org>

> From: New, Cecil (GEAE) [mailto:cecil.new@ae.ge.com]
>
> I have noticed that when I kill/interrupt an indexing process, that it
> leaves a "lock" file, preventing further indexing.
>
> This raises a couple of questions:
> a. When I simply delete the file and restart the indexing, it
> seems to work.
> Is there a risk in doing this?

No, there is no risk. The index is never inconsistent, so long as only a
single process is modifying it. Removing lock files is the standard
crash-recovery method for Lucene.

> b. Can indexing be done in a concurrent fashion? For
> example, allowing
> multiple uploading of files over the web and doing
> incremental indexing as
> they arrive. In this situation, you may have several
> documents that need to
> be indexed simultaneously.

Lucene only supports index modification by a single process and using a
single IndexWriter object. However, the index update code is thread safe,
so that many threads may use the same IndexWriter instance concurrently to
add documents.

Doug

--
To unsubscribe, e-mail: <mailto:lucene-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-user-help@jakarta.apache.org>