lucene-dev mailing list archives

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


Steven Rowe commented on LUCENE-2960:

bq. How about an IWC base class, extended by IWCinit and IWClive. IWCinit has setters for
everything, and IW.getConfig() returns IWClive, which has no setters for things you can't
set on the fly.

I tried to implement this, but couldn't figure out a way to avoid code and javadoc duplication
and/or separation for the live setters, which need to be on both the init and live versions.
 Duplication/separation of this sort would be begging for trouble.  (The live setters can't
be on the base class because the init and live versions would have to return different types
to allow for proper chaining.)

> 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