[CONNECTORS-764] Hopcount logic fails to notice when the max number of hops is increased between crawls

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: ManifoldCF 1.3
• Fix Version/s: ManifoldCF 1.4
• Component/s: Framework crawler agent
• Assignee: Karl Wright
• Reporter: Karl Wright
• Created: 13/Aug/13 22:42
• Updated: 15/Aug/13 09:35
• Resolved: 14/Aug/13 11:39

Description

When you do something like the following:

(1) Set the max hops for a job relatively low
(2) Crawl
(3) Increase the max hops
(4) Crawl again

... the documents that are labeled with the state "Hop count exceeded" at the end of the first crawl are never touched again. This is because there are no additional links added to the intrinsiclink table during the second crawl, and thus the method reactivateHopcountRemovedRecords() is never called, leaving the documents in an incorrect state.