You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Florian Schmedding (JIRA)" <ji...@apache.org> on 2014/02/12 18:30:19 UTC
[jira] [Commented] (CONNECTORS-850) Maximum interval in dynamic
crawling
[ https://issues.apache.org/jira/browse/CONNECTORS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899304#comment-13899304 ]
Florian Schmedding commented on CONNECTORS-850:
-----------------------------------------------
I tested the feature now with Manifold 1.6 (build with ant). The maximum interval is respected. Should the interval drop below the maximum value after a document change was recognized? I would expect such a behavior but in a test this does not seem to be the case.
> Maximum interval in dynamic crawling
> ------------------------------------
>
> Key: CONNECTORS-850
> URL: https://issues.apache.org/jira/browse/CONNECTORS-850
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Framework crawler agent
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Florian Schmedding
> Assignee: Karl Wright
> Priority: Minor
> Labels: features
> Fix For: ManifoldCF 1.5
>
>
> Currently, the dynamic crawling method used for a continuous job extends the reseed and recrawl intervals when no changes are found in a checked document. However, it should be possible to restrict this extension to a maximum value in order to make sure that new documents are discovered within a certain interval.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)