From dev-return-19224-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Wed Feb 13 05:50:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id F1FB6180674 for ; Wed, 13 Feb 2019 06:50:03 +0100 (CET) Received: (qmail 3565 invoked by uid 500); 13 Feb 2019 05:50:03 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 3554 invoked by uid 99); 13 Feb 2019 05:50:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2019 05:50:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6F849CBE5A for ; Wed, 13 Feb 2019 05:50:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id JrhiqXi9bsS7 for ; Wed, 13 Feb 2019 05:50:00 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AF25E5F645 for ; Wed, 13 Feb 2019 05:50:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4C8F0E2789 for ; Wed, 13 Feb 2019 05:50:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 145C32449F for ; Wed, 13 Feb 2019 05:50:00 +0000 (UTC) Date: Wed, 13 Feb 2019 05:50:00 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1580) Issues in documentum connector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766799#comment-16766799 ] 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: https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs > 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)