[jira] [Resolved] (CONNECTORS-983) Rethink how document version string is used in IRepositoryConnector for communicating "always retry" and "delete document"

["Karl Wright (JIRA)" <ji...@apache.org>]

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

Karl Wright resolved CONNECTORS-983.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: ManifoldCF 2.0)
                   ManifoldCF 1.7

Was resolved months ago

> Rethink how document version string is used in IRepositoryConnector for communicating "always retry" and "delete document"
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-983
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-983
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 2.0
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.7
>
>
> Right now, all IPipelineConnector implementations require specification information to be packed into a version string.  This is enforced by the fact that the methods that use this information do not receive a Specification object with which to work directly -- which guarantees consistency between version string and what is indexed.
> IRepositoryConnector, on the other hand, still passes Specification objects to all methods.  This is in part because version strings in IRepositoryConnector have an extended meaning: a blank value means that the document must be refetched on the very next crawl attempt.  It would be better, perhaps, to separate these concerns and come up with a common way of dealing with version strings.



--
This message was sent by Atlassian JIRA
(v6.2#6252)