manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Muhammed Olgun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1077) Add activity logging for decision and exception events across all connectors
Date Mon, 20 Oct 2014 18:17:34 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177237#comment-14177237
] 

Muhammed Olgun commented on CONNECTORS-1077:
--------------------------------------------

Hi Karl,

I checked "Result code match:" search in crawler ui. It has very good search capability. Even
I searched for "K" and all documents which have "OK" result code returned. So I think status
code should be its exception name. Probably if user search for EXCEPTION then all exception
status codes will return. Actually, I didn't know that such a searching capability. Thats
why I used only EXCEPTION status code for all exceptions.

> Add activity logging for decision and exception events across all connectors
> ----------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1077
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1077
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Alfresco connector
>    Affects Versions: ManifoldCF 2.0
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 2.0
>
>
> 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
history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message