Thanks Karl.
On Tue, Nov 26, 2019 at 1:39 PM Karl Wright wrote:
> No, just changing the job characteristics will NOT cause the incremental
> behavior to be erased.
>
> Karl
>
>
> On Mon, Nov 25, 2019 at 10:20 PM Sreejith Variyath <
> sreejith.variy...@tarams.com> wrote:
>
>> Yes. I understood.
No, just changing the job characteristics will NOT cause the incremental
behavior to be erased.
Karl
On Mon, Nov 25, 2019 at 10:20 PM Sreejith Variyath <
sreejith.variy...@tarams.com> wrote:
> Yes. I understood. Thanks Karl.
>
> I have another question. If I update job type from
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 wrote:
> One of the characteristics of continuous
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,
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
Hi Babita,
How you use continuous crawling depends on what you are trying to
accomplish with it. In the continuous crawling model, ManifoldCF requeues
documents after it crawls them, and checks them again after an interval
that is determined in part by how often they've changed in the past. The
