lucene-dev mailing list archives

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


Shay Banon commented on LUCENE-2960:

Just a note regarding the IWC and being able to consult it for live changes, it feels strange
to me that settings something on the config will affect the IW in real time. Maybe its just
me, but it feels nicer to have the "live" setters on IW compared to IWC.

I also like the ability to decouple construction time configuration through IWC, and live
settings through setters on IW. It is then very clear what can be set on construction time,
and what can be set on a live IW. It also allows for compile time / static check for the code
what can be changed at what lifecycle phase.

> 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