[LUCENE-636] [PATCH] Differently configured Lucene 'instances' in same JVM

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 3.0
• Assignee: Unassigned
• Reporter: Johan Stuyts
• Created: 27/Jul/06 08:38
• Updated: 28/Aug/22 11:29
• Resolved: 08/Dec/09 04:24

Description

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.

Issue Links

• incorporates: LUCENE-670 improper isolation (overuse of system properties) allows Lucene apps to clobber each other