[NIFI-5339] Better Time Tracking for ExecuteSQL Durations

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Component/s: Extensions
• Assignee: Peter Wicks
• Reporter: Peter Wicks
• Created: 26/Jun/18 16:23
• Updated: 29/Jun/18 14:48
• Resolved: 29/Jun/18 13:00

Description

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.

Issue Links

• links to: GitHub Pull Request #2817
• links to: GitHub Pull Request #2824