[
https://issues.apache.org/jira/browse/NIFI-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671571#comment-16671571
]
ASF GitHub Bot commented on NIFI-5744:
--------------------------------------
Github user yjhyjhyjh0 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3107#discussion_r230031051
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java
---
@@ -83,6 +83,8 @@
@WritesAttribute(attribute = "executesql.query.fetchtime",
description = "Duration of the result set fetch time in milliseconds"),
@WritesAttribute(attribute = "executesql.resultset.index",
description = "Assuming multiple result sets are returned, "
+ "the zero based index of this result set."),
+ @WritesAttribute(attribute = "executesql.error.message",
description = "If processing an incoming flow file causes "
+ + "an Exception, the flow file is routed to failure and
this attribute is set to the exception message."),
--- End diff --
Sure, thanks for the correction.
> 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)