On Fri, 2004-01-23 at 16:14, Wallmer, Martin wrote:
> Hi,
> 
> > -----Original Message-----
> > From: news [mailto:[EMAIL PROTECTED] Behalf Of Martin Holz
> > Sent: Freitag, 23. Januar 2004 15:55
> > To: [EMAIL PROTECTED]
> > Subject: Re: Integrate Indexstore and SEARCH (was Indexing store)
> > 
> > 
> > "Wallmer, Martin" <[EMAIL PROTECTED]> writes:
> > 
> > > > > 
> > > > > A question to the Lucene experts: Where does Lucene writes 
> > > > its index?
> > > > > Is it possible to store in RDBMS?
> > > > 
> > > > I was wondering about this as well. Another real problem 
> > > > might be when 
> > > > to index and transactionality. If we index as soon as we write a 
> > > > resource and then decide to rollback at some point it might 
> > > > be a problem 
> > > > if we updated a main index. It might be necessary to create a 
> > > > new index 
> > > > and merge it with the existing one on commit.
> > > > 
> > > 
> > > Ah ja, transactions :-(. The indexer must be a store and must
> > > take part at the two phase commit. How can this be achieved with
> > > Lucene? No big problem if Lucene can write its index to RDBMS...
> > 
> > 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.
> 
yeah, we have done this. A Directory implementation that store index in
database. So it become transaction aware.
> Martin
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to