[
https://issues.apache.org/jira/browse/CONNECTORS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763725#comment-16763725
]
Karl Wright commented on CONNECTORS-1580:
-----------------------------------------
{quote}
The documents which have already got indexed are getting processed but not
getting updated to Elasticsearch while re-running the same job
{quote}
What does the Simple History say here? Look for a document that you think
should be updated but isn't getting updated. Do you see a document fetch? Do
you see a document ingestion?
If you see an ingestion BUT the ES index is not getting updated then your
problem has to do with how ES is set up. I can imagine quite a few scenarios
where that can occur.
If you are seeing a fetch but no indexing, that means that the version string
for your documentum documents is not changing for some reason. This would
require more analysis, starting with learning exactly what has changed with the
document in question that you expect should cause a reindex. It is possible
you have some custom information that is not showing up in the version string
and you are nonetheless expecting it to. We would need more details to be able
to fix that.
> 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)
