[CT-1605] [Bug] generate_source sometimes fails without explanation

[jaredx435k2d0]

Is this a new bug in dbt-snowflake?

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

Current Behavior

If I run dbt run-operation generate_source --args '{"schema_name": "my_schema_name", "database_name": "my_db_name"}'

The output will sometimes be:

version: 2

sources:
  - name: my_schema_name
    database: my_db_name
    tables:

Other times, it works great.

Expected Behavior

I would expect a full sources document to be created, with each table, always.

Steps To Reproduce

It consistently happens with the same schemas, but I'm not sure why. Run dbt run-operation generate_source --args '{"schema_name": "my_schema_name", "database_name": "my_db_name"}' See that output never gets to the first table.

Both schemas for which I'm currently seeing this problem are populated via Fivetran's Google Sheets connector, and have _ROW as their first column

Still, I have other schemas populated by the same connector (in the same DB), with tables that have the same first column name, that work great with this command.

Relevant log output

I don't see any logs for this, nor error messages.

Environment

- OS: macOS 12.6.1 (21G217)
- Python: Python 3.10.7
- dbt-core:
- dbt-snowflake: 1.3.0

Additional Context

No response

[dbeatty10]

@jaredx435k2d0 this looks like it's related to the generate_source macro within the codegen package, so I'm going to transfer this issue over there for its maintainers to troubleshoot further.

If the root cause(s) end up being in the dbt-snowflake repo, then they can transfer this issue back again.

[boblannon-fp]

this looks related to my issue, i think... under "additional context" I included my findings. It seems to have to do with the fact that snowflake returns column names in all-caps.

https://github.com/dbt-labs/dbt-codegen/issues/82

[github-actions[bot]]

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.

[github-actions[bot]]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.