-
Notifications
You must be signed in to change notification settings - Fork 16
column_type override not being honoured for dbt seed #17
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
Labels
bug
Something isn't working
Comments
Did some debugging, apparently the table is correctly created, but some issue with the insert: `create table s3test.ref__populations (country_code string,population BIGINT)
` |
tovganesh
added a commit
that referenced
this issue
Apr 6, 2022
See: Issue#17 #17 Internal Ticket: https://jira.cloudera.com/browse/DBT-78 Testplan: Please follow the steps in Issue#17
Thanks @tovganesh - works perfectly |
tovganesh
added a commit
that referenced
this issue
Apr 8, 2022
See: Issue#17 #17 Internal Ticket: https://jira.cloudera.com/browse/DBT-78 Testplan: Please follow the steps in Issue#17
Fix has been merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
create a seed with 2 cols
Running
dbt seed
fails due to typeINT
being inferred, but some values are too large forINT
and requireBIGINT
.Create a schema.yml for the seed to overrise the inferred type to
BIGINT
Use
dbt seed --full-refresh
to ensure the new schema is used.Fails as the over ride is not honoured.
Sounds similar to dbt-labs/dbt-spark#139 seen on dbt-spark
The text was updated successfully, but these errors were encountered: