lucene-dev mailing list archives

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


Mark Miller commented on LUCENE-2960:

The current patch achieves this – the 99% of "simple" users that just
want to config IW and create it find all of the config in one place.
The 1% complex cases (need to change live settings) are able to do so,
but must read the jdocs for each setter to verify it's supported. 

The proposed alternatives sound just as good as this? In the proposed compromises, the 99%
of simple users will see have one place to config IW as well for the avg 'set up front' use
case. Perhaps the complex users could also have an API with a better pattern and it doesn't
have to be either or as you seem to lead...

An IWC that is 'partially' live and can be changed externally after passing to the IW is just
an inferior pattern plain and simple, and doesn't gain you much.

API should be designed around the simple users not the complex ones,
as the current patch does.

This really depends. If the simple users can be satisfied, and the API can also be decent
for complex users, win/win.

I guess I would place my bets that there will not be a ton of deprecations loops of settings
wanting to be live.

> 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
>         Attachments: LUCENE-2960.patch
> 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