-
Notifications
You must be signed in to change notification settings - Fork 235
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-454] [Bug] api.Column.string_type
causes error
#715
Comments
api.Column.string_type
causes errorapi.Column.string_type
causes error
Thanks @rlh1994 ! |
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. |
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. |
Is this a new bug in dbt-spark?
Current Behavior
Because there is no overwritten function, it uses a the core class, which is
character varying
which doesn't exist in spark (or databricks), so this api call just errors in spark/databricks targets.Expected Behavior
Model to pass, likely using
string
as the type.Steps To Reproduce
The easiest way to see it is with a basic model that just casts something to the string type:
Which in the case of a databricks target leads to the following compiled code
and a
dbt run
gives the error outputRelevant log output
No response
Environment
Additional Context
Issues in BQ: dbt-labs/dbt-bigquery#665
dbt-core relevant issue: dbt-labs/dbt-adapters#81
The text was updated successfully, but these errors were encountered: