[
https://issues.apache.org/jira/browse/CONNECTORS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128260#comment-13128260
]
Karl Wright commented on CONNECTORS-187:
----------------------------------------
This is a bit more subtle. The reason the document is on the processDeleteList
in the first place is because a version check has been done on it and the
document has been found to be missing. So if the document is returned to the
queue in its original form, this will force the crawler to perform a new
version check on the document when the retry occurs.
This is not unreasonable, but it is extra work that the crawler must undertake.
> WorkerThread method processDeleteList does not handle ServiceInterruptions
> from output connector optimally
> ----------------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-187
> URL: https://issues.apache.org/jira/browse/CONNECTORS-187
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework crawler agent
> Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 0.4
>
>
> The processDeleteList method in WorkerThread does not handle
> ServiceInterruption exceptions optimally; it just waits five minutes and
> retries. What it should do is requeue all the affected documents for the
> prescribed time, ignoring the possibility of "failure" or "skip", since
> neither of these can be performed when the output connection is not working.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
