-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add query_id
of last executed statement to Adapter Response
#891
Conversation
I want to be able to capture the `query_id` of the statement used to load a model. I ripped this off of the dbt-snowflake adapter and how they are setting `query_id` on the adapter response: https://github.com/dbt-labs/dbt-snowflake/blob/f95b9192f6eec9af4e30eaab87f9e3412febf7d1/dbt/adapters/snowflake/connections.py#L456-L461 I'm sure this doesn't handle 100% of accurately capturing the correct query ID for a particular load (I'm sure there are cases where multiple statements are run in order to perform the model or snapshot load), but I think this is a good start.
Well there is definitely a side effect to running the
|
This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days. |
Although we are closing this PR as stale, it can still be reopened to continue development. Just add a comment to notify the maintainers. |
resolves dbt-labs/dbt-adapters#630
docs dbt-labs/docs.getdbt.com/#
Problem
I want to be able to capture the
query_id
of the statement used to load a model.Solution
I ripped this off of the dbt-snowflake adapter and how they are setting
query_id
on the adapter response:https://github.com/dbt-labs/dbt-snowflake/blob/f95b9192f6eec9af4e30eaab87f9e3412febf7d1/dbt/adapters/snowflake/connections.py#L456-L461
I realize it is different from Snowflake in that appears that the query ID is available directly on the
cursor
object, and with Redshift you need to use thepg_last_query_id()
function in order to get the query ID.I'm sure this doesn't handle 100% of accurately capturing the correct query ID for a particular load (I'm sure there are cases where multiple statements are run in order to perform the model or snapshot load), but I think this is a good start.
Please let me know what I'm missing here in the potential of this breaking something else due to injecting another another query into a model load flow.
Checklist