lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-2960) Allow (or bring back) the ability to setRAMBufferSizeMB on an open IndexWriter
Date Fri, 11 Mar 2011 16:13:59 GMT


Michael McCandless commented on LUCENE-2960:

bq. Anyone's implementation can be live (i.e. the impl could change it's behavior over time
for whatever reason).

Well, that's really cheating.  I mean, yes, technically it's an out, so
it's certainly possible that an app can do the switching inside its
class... but that's not nice :)

EG if an app has LoadsAllDocsWarmer and VisitsAllPostingsWarmer (say)
and they want to switch between (for some reason)... they'd like have
to make a SegmentWarmerSwitcher class or something.

Seems silly because IW could care less if you switch up your warmer.
It just needs to get the current warmer every time it goes and warms
a segment...

> Allow (or bring back) the ability to setRAMBufferSizeMB on an open IndexWriter
> ------------------------------------------------------------------------------
>                 Key: LUCENE-2960
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Shay Banon
>            Priority: Blocker
>             Fix For: 3.1, 4.0
> In 3.1 the ability to setRAMBufferSizeMB is deprecated, and removed in trunk. It would
be great to be able to control that on a live IndexWriter. Other possible two methods that
would be great to bring back are setTermIndexInterval and setReaderTermsIndexDivisor. Most
of the other setters can actually be set on the MergePolicy itself, so no need for setters
for those (I think).

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message