You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/10/07 15:14:27 UTC

[jira] [Commented] (NIFI-974) Improve error messages included in Exceptions that are thrown by ProcessSession

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

Mark Payne commented on NIFI-974:
---------------------------------

Though not actually in the ProcessSession, another error that I have seen recently that threw me for a loop when using Site-to-Site: "User DN is not known". This should have been much more informative, such as "Could not find any account for user with Distinguished Name <insert DN here>. If you believe the user account does exist, please contact your administrator to ensure that the Authorization Providers are properly configured for your environment."

> Improve error messages included in Exceptions that are thrown by ProcessSession
> -------------------------------------------------------------------------------
>
>                 Key: NIFI-974
>                 URL: https://issues.apache.org/jira/browse/NIFI-974
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Mark Payne
>             Fix For: 0.4.0
>
>
> Exceptions that are thrown by StandardProcessSession tend to be geared toward verbiage that makes sense within the context of the ProcessSession, but they don't make much sense within the context of a Processor. Developers are often confused by the meaning.
> Examples include:
> "... is not the most recent version of this FlowFIle." This should note that the processor modified the FlowFIle via write, putAttribute, putAllAttributes, etc. and then attempted to access an old version of the FlowFile
> "transfer relationship not specified". This should note that the Processor has a bug that resulted in a FlowFile not being transferred or removed and that all FlowFiles must be accounted for; this message should also indicate whether the FlowFile was created in this session or if the FlowFile was consumed from a queue.
> There are likely other examples of poorly worded Exceptions.



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