Skip to content
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

Update dbt debug to also check that the database and warehouse fields are correct #1118

Closed
2 tasks done
sidpatel13 opened this issue Jul 17, 2024 · 2 comments
Closed
2 tasks done
Labels
enhancement New feature or request

Comments

@sidpatel13
Copy link

Is this a new bug in dbt-snowflake?

  • I believe this is a new bug in dbt-snowflake
  • I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Currently dbt debug runs select 1 as id (link). And seems like snowflake will allow you to do that without correct database/warehouse. This means that this command will pass regardless of whether the warehouse, database info provided is correct.

Expected Behavior

dbt debug should fail if the warehouse or database info is incorrect.

Steps To Reproduce

Run dbt debug with wrong config values for database and warehouse. It will still pass.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-snowflake:

Additional Context

No response

@sidpatel13 sidpatel13 added bug Something isn't working triage labels Jul 17, 2024
@graciegoheen graciegoheen added enhancement New feature or request and removed bug Something isn't working labels Jul 24, 2024
@graciegoheen graciegoheen changed the title [Bug] Update dbt debug to also check that the database and warehouse fields are correct Update dbt debug to also check that the database and warehouse fields are correct Jul 24, 2024
@amychen1776
Copy link

Taking a look at this - this is expected behavior even in Snowflake
image

For the debug command that we are running (select 1 as id) - it makes sense that it wouldn't check the database. We aren't selecting an object in the database. For that, I don't see us updating. For warehouse - this would be an enhancement, even on Snowflake's capabilities with that query.

@amychen1776
Copy link

At this time, this is not something we intend to change because the behavior is expected on Snowflake.

@amychen1776 amychen1776 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants