You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2018/09/20 09:04:00 UTC

[jira] [Updated] (CONNECTORS-1497) Re-index seeded modified documents when the re-crawl interval is infinity and connector model is MODEL_ADD_CHANGE

     [ https://issues.apache.org/jira/browse/CONNECTORS-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright updated CONNECTORS-1497:
------------------------------------
    Fix Version/s: ManifoldCF next

> Re-index seeded modified documents when the re-crawl interval is infinity and   connector model is MODEL_ADD_CHANGE
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1497
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1497
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework agents process
>    Affects Versions: ManifoldCF 2.9.1
>            Reporter: Ahmed Mahfouz
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF next
>
>         Attachments: CONNECTORS-1497.patch, CONNECTORS-1497.patch2, CONNECTORS-1497.patch3
>
>
> Trying to avoid a full scan of all documents for a better efficiency with a large number of documents. I tried so many different setting for the Jobs but I couldn't accomplish that. Especially when the repository connector model is MODEL_ADD_CHANGE I was expecting the modified documents seeded should be re-indexed immediately similar to the new seeds but I found out it uses the re-crawl time as the scheduled time and it waits for the full scan to get re-indexed. I avoided full scan by setting the re-crawl interval to infinity but still, my modified documents seeds were not getting indexed. After digging into the code for quite good time. I did some modification to the JobManager and it worked for me. I would like to share the change with you for review so I opened this ticket.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)