manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1580) Issues in documentum connector
Date Fri, 08 Feb 2019 08:26:00 GMT

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

Karl Wright commented on CONNECTORS-1580:
-----------------------------------------

Hi,
I can make almost no sense of this ticket.

Can you describe the job scheduling setup?  Specifically is this "scan once" or "rescan dynamically"?
 What does this mean exactly? "We have scheduled incremental crawling for every 15 mins"

You should be aware that the document count will vary because documents that are discovered
are then processed and ManifoldCF may determine during processing that the document does not
need to be indexed.  The best way to figure out what MCF is doing is to look at the Simple
History report and see what is happening.  You can see what is fetched and what is reindexed
that way.

Can you include the Simple History for one incremental job run here, and describe what is
wrong with it?


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