lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Geis (JIRA)" <>
Subject [jira] Commented: (LUCENE-636) [PATCH] Differently configured Lucene 'instances' in same JVM
Date Thu, 05 Apr 2007 03:24:32 GMT


Ken Geis commented on LUCENE-636:

This is not going to be sufficient.  There are active code paths that still use System.getProperty(..).
 For instance, the static initializers of FSDirectory and SegmentReader.

If I load up a Compass-based web app, and it uses an old version of Lucene that works off
system properties, it will set the org.apache.lucene.SegmentReader.class property to use a
Compass-specific segment reader.  Then in another web app that uses a current version of Lucene
that has "moved away from using system properties," the application will crash when it tries
to load the SegmentReader class.

> [PATCH] Differently configured Lucene 'instances' in same JVM
> -------------------------------------------------------------
>                 Key: LUCENE-636
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Johan Stuyts
>         Attachments: Lucene2DifferentConfigurations.patch
> Currently Lucene can be configured using system properties. When running multiple 'instances'
of Lucene for different purposes in the same JVM, it is not possible to use different settings
for each 'instance'.
> I made changes to some Lucene classes so you can pass a configuration to that class.
The Lucene 'instance' will use the settings from that configuration. The changes do not effect
the API and/or the current behavior so are backwards compatible.
> In addition to the changes above I also made the SegmentReader and SegmentTermDocs extensible
outside of their package. I would appreciate the inclusion of these changes but don't mind
creating a separate issue for them.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message