manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: Running 2 jobs to update same document Index but different
Date Fri, 30 Mar 2012 10:51:17 GMT
I did not see that you tried creating a filesystem connection and job.
 Did you do that, and did it work for you without sending a deletion?
If not, please go back to using the manifoldcf id field and try that

Here is the patch I'd like you to apply:

--- framework/agents/src/main/java/org/apache/manifoldcf/agents/incrementalingest/
+++ framework/agents/src/main/java/org/apache/manifoldcf/agents/incrementalingest/
@@ -697,6 +697,8 @@
     IOutputConnection connection =

+    Logging.ingest.error("Deleting documents!", new
Exception("Deletion stack trace"));
     if (Logging.ingest.isDebugEnabled())
       int i = 0;

Then, rebuild ManifoldCF.  Every document that is deleted from the
index will generate a trace in the log.  Run your crawl and send me
one of those traces.


On Fri, Mar 30, 2012 at 6:06 AM, Anupam Bhattacharya
<> wrote:
> I checked the Manifoldcf logs and i there were no exceptions.
> Additionally i changed the id (uniqueKey) in SOLR to the documentum specific
> unique id i.e. r_object_id and ran the job. This i time i could easily
> create the indexes.
> For (4) please provide the places for which i need to enable logging.
> On Thu, Mar 29, 2012 at 6:56 PM, Karl Wright <> wrote:
>> "But as per my observation the deletion happens only when uniqueKey in
>> SOLR schema is set to id. "
>> The SOLR setup cannot influence the flow in ManifoldCF unless it causes
>> SOLR to reject the ManifoldCF requests.  So I suspect that the delete
>> request is happening in both cases, and it is not getting acted upon by SOLR
>> in the case where uniqueKey is not set to "id".  That's because the delete
>> request from ManifoldCF will be for a key that solr doesn't recognize as
>> such.
>> Please do try recommendations (3) and (4).
>> Karl

View raw message