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.sreej...@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 >
