lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: Using IndexWriterConfig repeatedly in 3.1
Date Fri, 01 Apr 2011 20:44:04 GMT
The issue is that a MergePolicy instance cannot be re-used across
multiple writers.

So, you could take your first IWC, change out the MergePolicy, then re-use it?

Other things also cannot be reused, eg a ConcurrentMergeScheduler instance.

Mike

http://blog.mikemccandless.com

On Fri, Apr 1, 2011 at 4:07 PM, Christopher Condit <condit@sdsc.edu> wrote:
> I see in the JavaDoc for IndexWriterConfig that:
> "Note that IndexWriter makes a private clone; if you need to
> subsequently change settings use IndexWriter.getConfig()."
>
> However when I attempt to use the same IndexWriterConfig to create
> multiple IndexWriters the following exception is thrown:
>
> org.apache.lucene.util.SetOnce$AlreadySetException: The object cannot be
> set twice!
>        at org.apache.lucene.util.SetOnce.set(SetOnce.java:69)
>        at org.apache.lucene.index.MergePolicy.setIndexWriter(MergePolicy.java:263)
>        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1078)
>
> Is this the intended design? Is there a way to use the configuration
> multiple times? I see that clone won't work since it's shallow...
>
> Thanks,
> -Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message