[
https://issues.apache.org/jira/browse/LUCENE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-636.
--------------------------------
Resolution: Fixed
Fix Version/s: 3.0
> [PATCH] Differently configured Lucene 'instances' in same JVM
> -------------------------------------------------------------
>
> Key: LUCENE-636
> URL: https://issues.apache.org/jira/browse/LUCENE-636
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Johan Stuyts
> Fix For: 3.0
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
