[
https://issues.apache.org/jira/browse/NIFI-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664528#comment-16664528
]
ASF GitHub Bot commented on NIFI-5744:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/3107
Just to connect the dots here, there is some dissent from the PMC about
this approach, so we should do our best to reach consensus on the mailing list
before this PR is merged, in case the direction changes (switch from an
attribute to additional outgoing relationships, e.g.)
> Put exception message to attribute while ExecuteSQL fail
> --------------------------------------------------------
>
> Key: NIFI-5744
> URL: https://issues.apache.org/jira/browse/NIFI-5744
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.7.1
> Reporter: Deon Huang
> Assignee: Deon Huang
> Priority: Minor
>
> In some scenario, it would be great if we could have different behavior based
> on exception.
> Better error tracking afterwards in attribute format instead of tracking in
> log.
> For example, if it’s connection refused exception due to wrong url.
> We won’t want to retry and error message attribute would be helpful to keep
> track of.
> While it’s other scenario that database temporary unavailable, we should
> retry it based on should retry exception.
> Should be a quick fix at AbstractExecuteSQL before transfer flowfile to
> failure relationship
> {code:java}
> session.transfer(fileToProcess, REL_FAILURE);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
