manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sreejith Variyath <sreejith.variy...@tarams.com>
Subject Re: Continues Job
Date Tue, 26 Nov 2019 03:20:09 GMT
Yes. I understood. Thanks Karl.

I have another question. If I update job type from  TYPE_SPECIFIED  to
TYPE_CONTINUOUS , Then the document versioning will reset and job will pick
all the documents again?.

On Tue, Nov 26, 2019, 05:12 Karl Wright <daddywri@gmail.com> wrote:

> One of the characteristics of continuous jobs is that they call
> addSeedDocuments multiple times on a single job run.  The job run never
> ends, so this is how the job picks up documents for the infinitely-running
> job.  That's just the way it works.  Have you read the book?
>
> Karl
>
>
> On Mon, Nov 25, 2019 at 5:37 PM SREEJITH va <va.sreejith@gmail.com> wrote:
>
>> Hi Every One,
>>
>> I am trying to setup a job which is having a JDBC repository connector.
>> One transformation connector and a custom output connector.
>>
>> I want this job needs to run in two mode.
>>
>>    - Sample Mode : This is a sample migration mode. Job will pick 10
>>    documents and migrate to output repository. Then pause the job. I am
>>    planning to pause the job using quartz job depends on the document
>>    processing and document in queue count. This sample run can do "n" times.
>>    - Actual Mode : This is the actual migration mode. In this mode, The
>>    same job needs to runs continuously. The remaining documents after the
>>    sample migration and also any new documents should pick and migrate.
>>
>> Could any one please help me on what schedule settings I should follow
>> for this kind of job.  Currently I tried with following settings
>>
>>             jobDescription.setStartMethod(IJobDescription.START_DISABLE);
>>             jobDescription.setType(IJobDescription.TYPE_CONTINUOUS);
>>             jobDescription.setInterval(300000l);
>>             jobDescription.setReseedInterval(120000l);
>>
>> Also I have idNodeQuery set to pick 10 documents  (in sample mode) in the
>> JDBC repo connector. But during the job startup in sample mode,
>> The addSeedDocuments(...) API getting invoked twice and it causing to
>> process more than 10 documents. I do have version query. And the documents
>> are not processing in subsequent runs unless there is a version change.
>>
>> Really appreciate if some one can help me on these two queries.
>>
>>
>>
>>
>>
>> --
>> Regards
>> -Sreejith
>>
>

-- 
www.tarams.com <https://www.tarams.com/>    
=============================

DISCLAIMER:
 The information in this message is confidential and may be 
legally 
privileged. It is intended solely for the addressee. Access to 
this 
message by anyone else is unauthorized. If you are not the intended 

recipient, any disclosure, copying, or distribution of the message, or 
any 
action or omission taken by you in reliance on it, is prohibited and
 may 
be unlawful. Please immediately contact the sender if you have 
received 
this message in error. Further, this e-mail may contain viruses
 and all 
reasonable precaution to minimize the risk arising there from 
is taken by 
Tarams. Tarams is not liable for any damage sustained by you
 as a result 
of any virus in this e-mail. All applicable virus checks 
should be carried 
out by you before opening this e-mail or any 
attachment thereto.
Thank you 
- Tarams Software Technologies Pvt.Ltd.
=============================

Mime
View raw message