You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2016/04/11 20:04:25 UTC

[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.

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

Joseph Witt commented on NIFI-1754:
-----------------------------------

An easy way to do this would be have some sort of debug/toString variant on ProcessSession which would log the toString of any FlowFiles involved in that session ordered by things it pull from its queues, then things it created, and so on.

> Rollback log messages should include the flowfile filename and UUID to assist in flow management.
> -------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1754
>                 URL: https://issues.apache.org/jira/browse/NIFI-1754
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.0.0, 0.7.0
>            Reporter: Joe Skora
>
> When a processor calls rollback on a flowfile, the filename and UUID of the flowfile should be included in log entry to make it easier for the offending files to be found and fixed or removed from the flow by the dataflow managers.



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