-
Notifications
You must be signed in to change notification settings - Fork 59
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
[CT-1909] [CT-1903] Unable to generate docs from dbt core #281
Comments
Thanks for opening this issue @jaswanth-gaddipati ! Could you share more detail about the error it is throwing? i.e., could you share the relevant output and/or logs within |
I did some more research @jaswanth-gaddipati. I see now that you mentioned precise error was something like:
Could you try adding target: dev
outputs:
dev:
type: redshift
...
ra3_node: true # enables cross-database sources Apparently, this configuration should enable cross-database sources if you are not actually using RA3 nodes. One known problem is that dbt Cloud users do not have access to custom |
Hi @dbeatty10 Thank you. I am able to generate docs. One more question can we create models in redshift across DBs as it has cross db limitation. |
🙌 Awesome @jaswanth-gaddipati !
I don't think so due to the known limitations. I'm guessing you would need separate dbt projects per database. But if you discover that it does work somehow, please let us know! Since generating the docs is working for you now, I'm going to close this issue. You can open a new one if you run into any bugs or have any feature requests. |
Is this a new bug in dbt-core?
Current Behavior
dbt docs generate
throwing error
cross-db references allowed only in Redshift RA3.
but dbt compile is working properly
Expected Behavior
dbt docs generate should generate docs
Steps To Reproduce
define sources across dbs in redshift in dbt project
develop and execute models in a particular database
run dbt docs generate
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: