Hi Mike, > > I never saw the test suite before (shame on me). It will be VERY useful in > the future. Thank you very much!! >
No blame on you. You point out an important area where our documentation is lacking. > I have another question - maybe someone knows the answer: > > It seems that CLucene is keeping stuff in memory between the open/close of > the IndexWriter object. For example, if you create a brand new index and > create a document in it with just the field "TEST" containing "TEST", and > right after inserting it you search in the index for "TEST:TEST", without > closing the IndexWriter object, it will never be found. But, if you close > the IndexWriter before searching, and then search, it will find it. So my > question is: is there a way to change that behavior? I'd like all changes to > the index to be "instant" and to be able to search for newly created > documents right after inserting them. > You can open the IndexWriter with autoCommit set to true so it will commit the written documents to the segments file immediately, causing it to become visible to readers. For performance reasons, documents are still not written to the physical storage immediately, so you'll have to call IndexWriter::flush() after inserting a document. Best regards, Isidor ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ CLucene-developers mailing list CLucene-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clucene-developers
