Leo, >From my experience, as I update the index (without optimizing), the number of physical index files grows. I typically use the number of files as an indicator as to when optimization is required. While I don't think Lucene itself has any API to check this, a shell script or the application can do so easily.
HTH, Terry ----- Original Message ----- From: "Leo Galambos" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Sunday, February 02, 2003 9:48 AM Subject: Re: Wildchar based search?? | > On Sat, 1 Feb 2003, Rishabh Bajpai wrote: > > > also, i rememebr readin somewhere that one had to build the index in > > some special way, but since you say no; i will take that. i anyways dont > > rememebr where I read it, so no point asking about something if I am > > myself not sure.... > > I remember only one problem that is related to indexing phase - it is > ``optimize'' function. If you update your index, one cannot tell you if > you must also call optimize() or not. > > If you do not call it, it may slow down queries (I do not know how much, > but Otis told it). If you call it, it slows down the indexing phase (I > have tested it and it is significant). > > AFAIK Lucene cannot tell you when the index becomes dirty so that you must > call optimize. On the other hand it does not affect small indexes, where > optimize() costs nothing. > > Otis, I think that this still holds. Right? > > -g- > > > > --------------------------------------------------------------------- > 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]
