[
https://issues.apache.org/jira/browse/NIFI-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729979#comment-15729979
]
Aldrin Piri edited comment on NIFI-3148 at 12/7/16 9:37 PM:
------------------------------------------------------------
This is in linking to NIFI-2585:
The core ask between the two issues is fairly similar in nature from the
standpoint that we have some/all of this information available in provenance
but no way to make use of it to aid in some of the routing in a dynamic
fashion. Currently, users are required to introduce other processors that are
carrying out the functionality of tagging data despite already having that
context for it available.
was (Author: aldrin):
The core ask between the two issues is fairly similar in nature from the
standpoint that we have some/all of this information available in provenance
but no way to make use of it to aid in some of the routing in a dynamic
fashion. Currently, users are required to introduce other processors that are
carrying out the functionality of tagging data despite already having that
context for it available.
> 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)
