On 11/28/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
I think this (that under certain use cases, IndexWriter can create > mergeFactor segments even when maxMergeDocs is very large) is actually fairly serious. I wonder how many users are affected by this now. It's not called out currently in CHANGES.txt but I think it should be (this would be under LUCENE-672 I think)? Is there a simple way to characterize the cases when this would happen? Mike
http://www.nabble.com/flushRamSegments%28%29-is-%22over-merging%22--tf2108069.html#a5816291 If the number of buffered docs at the close plus the number of docs in the last non-ram segment was greater than mergeFactor, then a new segment would be created. Still doesn't roll off the toungue nicely, but I agree an update to CHANGES calling this out might be in order. -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
