[
https://issues.apache.org/jira/browse/NIFI-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722551#comment-15722551
]
Aldrin Piri commented on NIFI-3148:
-----------------------------------
Hey Andreas,
Thanks for creating this issue and sharing some of your areas to address. I do
think there are some commonalities we can tease out of this and should serve as
a nice basis for additional tickets and work.
> Universal Error Handling
> ------------------------
>
> Key: NIFI-3148
> URL: https://issues.apache.org/jira/browse/NIFI-3148
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Andreas Petter
> Priority: Minor
>
> For error handling processors (like a custom generic error handling processor
> doing some generic clean-up procedure in case of failure) it might be
> beneficial to be able to track:
> 1.) which connection the error came in (e.g. FetchSFTP has three different
> error handling relationships)
> 2.) have a way (like a common attribute name) to transport errors and error
> messages (e.g. Exceptions)
> 3.) maybe have special error tracking support in the ui (e.g. a checkbox to
> switch off processors only connected through error connections and things
> like that to increase comprehensibility of data flows)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
