[
https://issues.apache.org/jira/browse/CONNECTORS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763702#comment-16763702
]
Pavithra Dhakshinamurthy commented on CONNECTORS-1580:
------------------------------------------------------
Hi Karl,
Please find the screenshot below for job scheduling setup .
The documents which have already got indexed are getting processed but not
getting updated to Elasticsearch while re-running the same job, but we are
facing issue only with the documentum connector not with other MCF
connectors.Not sure if any seeding history is being maintained, if so can you
please share the method/code for resettting the seeding/deleting history for a
single job.
!Job_Scheduling.png!
Thanks&Regards,
Pavithra
> Issues in documentum connector
> ------------------------------
>
> Key: CONNECTORS-1580
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1580
> 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
(v7.6.3#76005)
