Open ann8ty opened 3 months ago
Hi! Trying to figure out what might be going on here. You mentioned "this is a per session attribute in redshift". I wonder if we're sending the statements to the database in a way that each statement becomes its own session. Would you be able to try it on 1.5
, which uses redshift-connector
instead of psycopg2
and see if the behavior is any different?
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.
Is this a new bug in dbt-core?
Current Behavior
Per doc https://docs.getdbt.com/reference/resource-configs/sql_header I've tried both:
we've also tried ON instead of TRUE
and the result is the column value is NULL when run through DBT, but the same query run through redshift query editor produces a value, leading us to believe that enable_case_sensitive_super_attribute isn't being set by DBT.
this is a per session attribute in redshift, unable to set as a parameter group
the rest of the dbt staging sql
Expected Behavior
expected DBT to work the same as redshift query editor
Steps To Reproduce
Relevant log output
Environment
Which database adapter are you using with dbt?
redshift
Additional Context
is it possibly not sql_header for redshift? there is no example for redshift.