-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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-3385] E: Credentials in profile "invalid: 'database' is a required property" with dbt-core 1.7.x #9080
Comments
Thanks for reaching out @VarunSharma15 ! The issue title says "database", but the error message you shared says "schema":
Is the issue title supposed to say "schema"? |
Hi @dbeatty10,
|
Thanks for that update @VarunSharma15 👍 Could you take a look in your logs ( |
Hi @dbeatty10 I am also attaching result of a testcase run |
Looking at a portion of your test case output, it looks like the underlying issue is a JSON schema validation error:
But the Did you try providing a value for |
@VarunSharma15 can you try and see ifhttps://github.com/Teradata/dbt-teradata/pull/127 resolves things? |
@dataders , we already tried this solution, but failed with the below error:
|
@tallamohan I'm going to close this issue in favor of our thread in the upgrade discussion, given that this is not an issue with dbt-core: #8307 (comment) |
Is this a new bug in dbt-core?
Current Behavior
With dbt-teradata adapter,
We are seeing an issue while running a sample project(jaffle shop) on local branch with dbt-core 1.7 .
We are getting the below mentioned error, although database is an optional property in our connections.py file.
Schema and database are same in Teradata database, sample project is working fine with previous versions until v1.6.7
Expected Behavior
dbt commands should pass without database property mentioned
Steps To Reproduce
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
dbt-teradata adapter
We found a similar issue on dbt-databricks
databricks/dbt-databricks#469
The text was updated successfully, but these errors were encountered: