One of the unfortunate aspects of Lucene is that the IndexReader doesn't update itself when the underlying index has been changed by an IndexWriter. You have to reopen the IndexReader to get the updated content. With Lucene 3, the cost of doing this has been improved with the new Near-Real-Time IndexReader, but you still have to manage the process.
H2 1.2.x, which uses lucene 2.4+ handles this by opening a new IndexReader on every query. Not optimal, for sure, but at least it's consistent. H2 1.3 uses Lucene 3 and will have a new system that keeps the IndexReader and IndexWriter open for the life of the server. It will maintain their consistency as the indexes are modified as well as provide a considerable performance boost for full- text search, especially on heavily-loaded systems. And hopefully, continue to provide up-to-date search results. Matt On Nov 16, 3:23 am, Wildam Martin <[email protected]> wrote: > On Tue, Nov 16, 2010 at 07:50, Sergi Vladykin <[email protected]> > wrote: > > Yes current build.xml is broken. You should manually downloadlucene > > 3.0 and add it to the class path instead of 2.2 version. > > Ah, thanks for the notice. > BTW: Anybody knows ifLucene3.0 still has issues with words not being > found even although should be indexed? > I experience this in various products usingLucene. > > -- > Martin Wildam > > http://www.google.com/profiles/mwildam -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
