-
Notifications
You must be signed in to change notification settings - Fork 60
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
[ADAP-500] [Bug] dbt-redshift 1.5 does not work with non-standard redshift hostnames #419
Comments
Yes, same issue. Using a CNAME record for the redshift host, therefore region is not present in the host. There needs to be some other way of specifying region, probably in |
Thanks for reporting this @kochalex and @padbk ! It looks like the Agreed with your recommended path forward of either adding a new Acceptance criteriaEither of the following is sufficient as exit criteria:
Implementation noteThe
|
…ft hostnames (#420) * Fix for region parsing in host name.WIP * Edge cases and cleanup * Minor nits * clean up aws regions invocation * Log message and doc nits * Changie entry * Skip validation if aws regions are not determined * move the regions var earlier to effectively cache
…ft hostnames (#420) * Fix for region parsing in host name.WIP * Edge cases and cleanup * Minor nits * clean up aws regions invocation * Log message and doc nits * Changie entry * Skip validation if aws regions are not determined * move the regions var earlier to effectively cache (cherry picked from commit b644963)
…ft hostnames (#420) (#421) * Fix for region parsing in host name.WIP * Edge cases and cleanup * Minor nits * clean up aws regions invocation * Log message and doc nits * Changie entry * Skip validation if aws regions are not determined * move the regions var earlier to effectively cache (cherry picked from commit b644963) Co-authored-by: Neelesh Salian <nssalian@users.noreply.github.com>
This should probably be documented as a breaking change in the 1.5 changelog as well. |
Looking into this, it seems like region isn't a required parameter at all at least if you are connecting with a username and password. Can we investigate if we can either not require region at all or only require it in situations where it is actually required? |
…d redshift hostnames (dbt-labs#420) * Fix for region parsing in host name.WIP * Edge cases and cleanup * Minor nits * clean up aws regions invocation * Log message and doc nits * Changie entry * Skip validation if aws regions are not determined * move the regions var earlier to effectively cache
Is this a new bug in dbt-redshift?
Current Behavior
When upgrading to dbt 1.5, I get an 'index out of range error' when attempting to use things that connect to the database.
This is related to using a non-standard hostname for redshift - in my case I am opening a SSH tunnel to Redshift and using localhost as the host.
Expected Behavior
It works with the same configuration as prior versions of DBT or allows a region configuration to side-step this issue.
Steps To Reproduce
profiles.yml
.Relevant log output
Environment
Additional Context
The adapter is hard-coded to parse the region from the host value.
dbt-redshift/dbt/adapters/redshift/connections.py
Line 102 in aa98c95
The text was updated successfully, but these errors were encountered: