manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Muhammed Olgun (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1077) Add activity logging for decision and exception events across all connectors
Date Thu, 30 Oct 2014 08:25:33 GMT


Muhammed Olgun commented on CONNECTORS-1077:

Hi Karl,

{quote}I notice that you are putting almost all error codes that you add for individual connectors
into IOutputHistoryActivity and IHistoryActivity.{quote}

I think you mean NULL_URL and BAD_URL. JDBC connector and GridFS connectors can use these
variables together. I also checked JDBC connector and it also uses NULL_URL and BAD_URL. That's
why I added them into IOutputHistoryActivity and IHistoryActivity.

{quote}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.{quote}

You are right I'm gonna add their explanation.

> 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