Thanks for the comments Yonik!
To minimize the number of reader open/closes on large persistent segments, I think the ability to apply deletes only before a merge is important. That might add a 4th method: doBeforeMerge()
I'm not sure I get this. Buffered deletes are only applied(flushed) during ram flush. No buffered deletes are applied in the merges of on-disk segments.
It would be nice to not have to continually open and close readers on segments that aren't involved in a merge. Is there a way to do this? If SegmentInfos had a cached reader, that seems like it would solve both problems. I haven't thought about it enough to figure out how doable it is though.
This is a good idea! One concern, however, is that caching readers will cause a larger memory footprint. Is it acceptable?
Ning, please do produce another patch to the latest trunk (but you might want to wait until after LUCENE-702 is sorted out.
Will do. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
