Or, if you have an update action on your pipeline, you can just do an update to 
the documents that are in the error state (after corrected the error state, if 
appropriate).  CPF is fired by triggers, and you can configure it to be 
triggered by create and/or update.

So if you have an update action, you can, for example, to a node replace of a 
node on the document and replace it with the same contents.  This is sort of 
like touch in a UNIX world.

-Danny

From: [email protected] 
[mailto:[email protected]] On Behalf Of Geert Josten
Sent: Thursday, October 24, 2013 7:46 AM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Reprocessing error documents in CPF

Hi Karthik,

I guess the simplest, and safest way is to re-ingest the original file. If your 
pipelines do a lot of transformation, how do you know how and where to continue 
processing?

But if necessary, you could simply change or flush the CPF-related 
(state/status/etc) properties of that document. You could simply use 
xdmp:document-set-properties for that purpose..

Cheers,
Geert

Van: 
[email protected]<mailto:[email protected]>
 
[mailto:[email protected]<mailto:[email protected]>]
 Namens 
[email protected]<mailto:[email protected]>
Verzonden: donderdag 24 oktober 2013 16:14
Aan: [email protected]<mailto:[email protected]>
Onderwerp: [MarkLogic Dev General] Reprocessing error documents in CPF

Hi,

How to reprocess error documents in CPF from the state where it erred out?
For ex: a document can go to error state due to some configuration issues in my 
pipeline file or I can explicitly throw an error from my xqy code.
In those scenarios, how to reprocess the document?

Thanks,
Karthik

This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful.
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to