lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers" <>
Subject RE: Does Lucene search over memory too?
Date Mon, 28 May 2007 17:36:55 GMT

think you can find your answer in the IndexWriter API:

The optional autoCommit argument to the constructors  controls visibility of the changes to
IndexReader instances reading the same index. When this is false, changes are not visible
until close() is called. Note that changes will still be flushed to the Directory as new files,
but are not committed (no new segments_N file is written referencing the new files) until
close() is called. If something goes terribly wrong (for example the JVM crashes) before close(),
then the index will reflect none of the changes made (it will remain in its starting state).
You can also call abort(), which closes the writer without committing any changes, and removes
any index files that had been flushed but are now unreferenced. This mode is useful for preventing
readers from refreshing at a bad time (for example after you've done all your deletes but
before you've done your adds). It can also be used to implement simple single-writer transactional
semantics ("all or none").

Regards Ard

> Hi,
>     Does Lucene search FSDirectory as well as buffered 
> in-memory docs while
> we are calling
>     Why I'm asking this is, I've indexed my doc with mergeFactor &
> Max.Buff.Docs = 50 and I've optimized and closed it at mid-night
> only.Beforeoptimization, my search gives partial matches and it does
> not give matches
> which is in memory.
>     To get all matches (inclusive of matches in memory),what 
> i have to do?
>     Shall I use writer.flush() to resolve this?
> Thanks in Advance
>              RSK

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message