You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2017/09/04 14:13:00 UTC
[jira] [Comment Edited] (CONNECTORS-1455) Option to skip documents
[ https://issues.apache.org/jira/browse/CONNECTORS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152649#comment-16152649 ]
Karl Wright edited comment on CONNECTORS-1455 at 9/4/17 2:12 PM:
-----------------------------------------------------------------
If files are locked, MCF assumes that they should become unlocked on a subsequent retry.
If they remain locked after 3 attempts, clearly they are not merely locked but are in a state that cannot be resolved. It would be appropriate to skip them in that case.
What I need to know, though, is what actual SmbException we're getting for "locked" files. There may be different error messages the connector can look for. If this is the right one, I can just change the behavior of that case:
{code}
SmbException thrown: The process cannot access the file because it is being used by another process.
{code}
was (Author: kwright@metacarta.com):
If files are locked, MCF assumes that they should become unlocked on a subsequent retry.
If they remain locked after 3 attempts, clearly they are not merely locked but are in a state that cannot be resolved. It would be appropriate to skip them in that case.
What I need to know, though, is what actual SmbException we're getting for "locked" files. There may be different error messages the connector can look for.
> Option to skip documents
> ------------------------
>
> Key: CONNECTORS-1455
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1455
> Project: ManifoldCF
> Issue Type: Wish
> Components: JCIFS connector
> Affects Versions: ManifoldCF 2.8
> Reporter: Julien Massiera
> Assignee: Karl Wright
> Priority: Minor
>
> I am referring to our discussion: http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201612.mbox/%3CCALUFAGDaWaSv+CvVN92PJ=XAOcr48wzX9iLi6HfHLT=2s-7UYg@mail.gmail.com%3E
> As a reminder of our discussion: In some cases, it would be good to be able to configure a job so that it can skip files after 3 (or N) ServiceInterruption instead of aborting the job.
> The example I mentionned in the thread was the following: when a job encounters locked files, an SmbException is thrown. As a result, after 3 ServiceInterruption, the job simply aborts but it would be better to skip those files. With this configurable new paramter, the job would still complete instead of aborting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)