manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1077) Add activity logging for decision and exception events across all connectors
Date Wed, 29 Oct 2014 12:04:33 GMT


Karl Wright commented on CONNECTORS-1077:

Hi Muhammed,

I notice that you are putting almost all error codes that you add for individual connectors
into IOutputHistoryActivity and IHistoryActivity.  I don't think this is a good idea, unless
the error code is clearly general in nature, and would apply to more than a specific connector.
 Remember, for backwards compatibility reasons, we will not be able to ever REMOVE codes from
these interfaces once a release occurs that includes them.

I think it is also important that all the error codes in these interfaces have a brief explanation
of what they mean, so that other people use them properly.


> Add activity logging for decision and exception events across all connectors
> ----------------------------------------------------------------------------
>                 Key: CONNECTORS-1077
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Alfresco connector
>    Affects Versions: ManifoldCF 2.0
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 2.0
>         Attachments: Example.patch, capture, elasticsearch_review.patch, elasticsearch_review2.patch
> Many document skip decisions or transient exceptions are only logged, and are not recorded
as history events.  This makes it necessary upon occasion to refer to the manifoldcf log for
basic diagnosis.  We should record activity events for most decisions and exceptions in the

This message was sent by Atlassian JIRA

View raw message