----- Original Message ----- From: "Martin Holz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 23, 2004 6:17 PM Subject: Re: Integrate Indexstore and SEARCH (was Indexing store)
> "Wallmer, Martin" <[EMAIL PROTECTED]> writes: > > > > Isn't the point of using Lucene, that it is lightweight and does > > > not require a RDBMS? Usually Lucene uses a directory for its index. > > > I suspect moving the index to RDBMS is not easy. > > > > > > > Ok, so then everybody using Lucene must know, that there is no transactionality. > > Thats the same as with simple filesystemstore, no transactions, unless you use > > TxFileStore. Architecture must allow two phase commit. I'm sure, there is someone, > > who makes Lucene (or another indexer) transaction aware, if it is really needed. > > 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. I think the main problem is to provide transactional search results. This is for sure no problem if the search is mapped to sql for rdbms search, but I don't know how to achieve this with lucene without to copy the whole index. I don't know if it possible to shadow some parts of the index by subindices for each node. By the way: We are currently thinking about (propriatary) webDAV-extensions for transaction handling. I think this will become very interesting for many applications. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
