[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500802
]
Michael Busch commented on LUCENE-887:
--------------------------------------
> I think we should keep it out of core (ie, as subclasses as you've done
> here) for now?
We could also add new methods (not abstract) to Directory:
boolean isInterruptable();
void interrupt();
void clearInterrupt();
By default isInterruptable() would return false and the other two wouldn't
do anything. Only some Directory implementations should then overwrite these
methods, like FSDirectory.
What I don't like about this is that we would have to make those methods
public, because IndexWriter has to call them.
> Interruptible segment merges
> ----------------------------
>
> Key: LUCENE-887
> URL: https://issues.apache.org/jira/browse/LUCENE-887
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Reporter: Michael Busch
> Priority: Minor
> Attachments: ExtendedIndexWriter.java
>
>
> Adds the ability to IndexWriter to interrupt an ongoing merge. This might be
> necessary when Lucene is e. g. running as a service and has to stop indexing
> within a certain period of time due to a shutdown request.
> A solution would be to add a new method shutdown() to IndexWriter which
> satisfies the following two requirements:
> - if a merge is happening, abort it
> - flush the buffered docs but do not trigger a merge
> See also discussions about this feature on java-dev:
> http://www.gossamer-threads.com/lists/lucene/java-dev/49008
--
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]
