You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion
Describe the feature
As a dbt user, I want to be able to quickly look up information about the set of queries associated with a dbt model run rather than just the final create/insert/update statement. While the query_id is powerful, the session_id can provided richer information back to Snowflake users to under the full lifecycle of queries executed.
To implement this feature, we could extend the SnowflakeAdapterResponse to include the session_id.
github-actionsbot
changed the title
[Feature] Include Snowflake session_id in run results response
[ADAP-1091] [Feature] Include Snowflake session_id in run results response
Jan 9, 2024
+1, being able to easily see all connected queries in a given model instead of just the final query would be be very helpful in debugging / potential optimization!
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Is this your first time submitting a feature request?
Describe the feature
As a dbt user, I want to be able to quickly look up information about the set of queries associated with a dbt model run rather than just the final create/insert/update statement. While the query_id is powerful, the session_id can provided richer information back to Snowflake users to under the full lifecycle of queries executed.
To implement this feature, we could extend the
SnowflakeAdapterResponse
to include the session_id.Describe alternatives you've considered
Similar to the alternatives discussed within #7, a post-hook might work, but not give an idea of the full lifecycle in case of failures.
Who will this benefit?
This would help dbt-snowflake users to more effectively debug and understand why their queries succeeded or failed.
Are you interested in contributing this feature?
Yes!
Anything else?
No response
The text was updated successfully, but these errors were encountered: