manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavithra Dhakshinamurthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1580) Issues in documentum connector
Date Mon, 11 Feb 2019 15:14:00 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765053#comment-16765053
] 

Pavithra Dhakshinamurthy commented on CONNECTORS-1580:
------------------------------------------------------

Thanks Karl,
The documents which have already got indexed are getting processed but not getting updated
to Elasticsearch while re-running the same job-*Working fine*

The below issue exists in documentum connector.Please help us to fix this issue.
1)We have scheduled a job to run for every 15 mins and we have written a query in the addSeedDocuments
method to get the document id.On each schedule of the job, query will return different set
of records.All the document id's have been added in the below method.

activities.addSeedDocument(documentIdentifier);

How to reset the seeded documents for the each schedule of the same job?




> 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)

Mime
View raw message