> > For my applications I have not need to access Lucene inside a transaction. > > WebDAV does not know about transactions, which span more than one HTTP > request anyway. > > So it would be fine, when the data are indexed immediately after the slide > transaction > > is committed. Just take care, that Lucene never sees data, which are not > committed. > > If the WebDAV request should return, before the data are indexed depends > on the > > application. Performance <=> Integrity. > > > > There is already the problem, that WebDAV requests sometime need a lot of > time > > and the client may timeout despite the server running fine. > > > > Martin > > > But how can be assured that the index is never corrupted or inconsistent if > the server breaks down while indexing? IMO indexing must be transaction > aware. And if it is transaction aware we could give the user the choice if > he wants to have synchronus (inner transaction indexing) or asynchronus > indexing.
Reindex everything, if necessary. I won't complain, if somebody implements a indexer which uses transactions. And I can see that some applications will need it. But for me a simpler solution would be fine. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
