Thanks Yonik! Poor wording on my part. I won't vary maxBufferedDocs, just am making flushRamSegments() public and calling it externally (properly synchronized), earlier than it would otherwise be called from ongoing addDocument-driven merging.
Sounds like this should work. Chuck Yonik Seeley wrote on 11/09/2006 08:37 AM: > On 11/9/06, Chuck Williams <[EMAIL PROTECTED]> wrote: >> My main concern is that the mergeFactor escalation merging logic will >> somehow behave poorly in the presence of dynamically varying initial >> segment sizes. > > Things will work as expected with varying segments sizes, but *not* > varying maxBufferedDocuments. The "level" of a segment is defined by > maxBufferedDocuments. > > If there were a solution to flush early w/o maxBufferedDocuments > changing, things would work fine. > > -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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
