[
https://issues.apache.org/jira/browse/NIFI-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527739#comment-16527739
]
ASF GitHub Bot commented on NIFI-5339:
--------------------------------------
Github user patricker commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2824#discussion_r199182375
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java
---
@@ -93,6 +93,8 @@
@WritesAttributes({
@WritesAttribute(attribute="executesql.row.count", description =
"Contains the number of rows returned in the select query"),
@WritesAttribute(attribute="executesql.query.duration", description =
"Duration of the query in milliseconds"),
--- End diff --
Updated.
> Better Time Tracking for ExecuteSQL Durations
> ---------------------------------------------
>
> Key: NIFI-5339
> URL: https://issues.apache.org/jira/browse/NIFI-5339
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Peter Wicks
> Assignee: Peter Wicks
> Priority: Minor
> Fix For: 1.8.0
>
>
> ExecuteSQL uses an attribute, `executesql.query.duration`, to track how long
> query execution and fetch took.
> For multiple result set queries this is a cumulative/running total, and is
> not specific to each query.
> Also, there is no separation between query execution and fetch times.
> Updates:
> * Add a dedicated property `executesql.query.executiontime` to track the
> base query execution time.
> * Add a dedicated property 'executesql.query.fetchtime` to track the per
> resultset fetch time.
> * Update the existing `executesql.query.duration` to be the sum of the other
> two times.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
