You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2017/03/16 21:10:41 UTC

[jira] [Created] (NIFI-3617) StandardProcessSession should log the associated Processor when it logs the 'Content Claim created' log messages

Mark Payne created NIFI-3617:
--------------------------------

             Summary: StandardProcessSession should log the associated Processor when it logs the 'Content Claim created' log messages
                 Key: NIFI-3617
                 URL: https://issues.apache.org/jira/browse/NIFI-3617
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Core Framework
            Reporter: Mark Payne
            Assignee: Mark Payne


StandardProcessSession has a logger that it uses named StandardProcessSession.claims and it logs at the DEBUG level when it creates Content Claim to write to. Unfortunately, the log message includes the toString() of the Content Claim and the associated FlowFile but not the associated Processor. For cases where a Processor continues to write to a Content Claim, it would be nice to have that information provided in the log message as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)