[
https://issues.apache.org/jira/browse/NIFI-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527748#comment-16527748
]
ASF subversion and git services commented on NIFI-5339:
-------------------------------------------------------
Commit a14dbc7dbe20d31e919d52e349efbabc73caf19f in nifi's branch
refs/heads/master from patricker
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a14dbc7 ]
NIFI-5339 - Better Time Tracking for ExecuteSQL Durations
Signed-off-by: Pierre Villard <[email protected]>
This closes #2824.
> 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)
