You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2018/06/29 13:00:00 UTC

[jira] [Updated] (NIFI-5339) Better Time Tracking for ExecuteSQL Durations

     [ https://issues.apache.org/jira/browse/NIFI-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard updated NIFI-5339:
---------------------------------
    Component/s:     (was: Core Framework)
                 Extensions

> 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
>
> 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)