[SPIKE] Investigate state of transactions
dataders opened this issue · 2 comments
dataders commented
Is this your first time submitting a feature request?
- I have read the expectations for open source contributors
- 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-redshift functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Several issues already exist that even today, transactions are not working in dbt-redshift as they should
Similar to dbt-labs/dbt-core#9980 but only for dbt-redshift. Less future looking, but rather backward looking. How can we get back to a previous state?
questions
- Will aws/amazon-redshift-python-driver#162 solve our problems, or is there more to do?
- how does the
autocommit
parameter introduced in #475 affect transaction behavior? - is there a way to expose
redshift_connector
's.commit()
method to users in jinja land instaed?
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response