manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1580) Issues in documentum connector
Date Wed, 13 Feb 2019 05:50:00 GMT


Karl Wright commented on CONNECTORS-1580:

You are on your own here.  You are trying to use it as a queuing engine, not an incremental
indexer.  You have not thought this out properly, clearly, because that's not what addSeedDocuments()
does.  So you must come up with a version string computation that reflects the fact that your
documents have changed and need to be reconsidered.  It will have to directly reference whatever
external queue you are using to stuff changed documents in.

You should maybe start by reading the book.  It's free.  Here:

> Issues in documentum connector
> ------------------------------
>                 Key: CONNECTORS-1580
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>            Reporter: Pavithra Dhakshinamurthy
>            Priority: Blocker
>         Attachments: Job_Scheduling.png
> Hi Team,
>  We are facing below issues in apache manifold documentum connector version 2.9.1.kindly
help us. 
>  1.During the first run of the job,documents are getting indexed to ElasticSearch.If
the same job is run after the completion,records are getting seeded,processed but not updated
to output connector.Once the document id is indexed,same document id is not able to update
it again in the same job. 
>  2.We have scheduled incremental crawling for every 15 mins and document count will vary
for every 15 mins. But in seeding it is not resetting the document count,once the job is completed.It's
getting added to last scheduled job count.
>    eg.1st schedule-10 documents 
>       2nd schedule-5 documents 
> In the 2nd scheduled of the job,the document count should be 5,but it is having document
count as 15. so it is keep on adding the dcouments id for every schedule and it is processing

This message was sent by Atlassian JIRA

View raw message