Add retry columns to query_history_enriched #170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are new columns in the Query History system view from Snowflake, and I'd like to have those available in the dbt model query_history_enriched.
This PR adds the following columns:
- name: query_retry_time_ms
description: Total execution time (in milliseconds) for query retries caused by actionable errors.
- name: query_retry_time_s
description: Total execution time (in seconds) for query retries caused by actionable errors.
- name: query_retry_cause
description: Error that caused the query to retry. If there is no query retry, the field is NULL.
- name: fault_handling_time_ms
description: Total execution time (in milliseconds) for query retries caused by errors that are not actionable.
- name: fault_handling_time_s
description: Total execution time (in seconds) for query retries caused by errors that are not actionable.