[
https://issues.apache.org/jira/browse/NIFI-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693406#comment-16693406
]
ASF subversion and git services commented on NIFI-5744:
-------------------------------------------------------
Commit 3c7012ffda777b4692e4ea8db042ee1943a7a66a in nifi's branch
refs/heads/master from yjhyjhyjh0
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3c7012f ]
NIFI-5744: Put exception message to attribute while ExecuteSQL fail
This closes #3107.
Signed-off-by: Peter Wicks <[email protected]>
> 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)
