-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remove the report
schema and its models
#122
Comments
This isn't a problem caused by the ...
START sql table model report.chicago_residential_parcel_sales_per_quarter_and_cpd_beat [RUN]
START sql table model report.chicago_residential_parcel_sales_per_quarter_and_cpd_district [RUN]
ERROR creating sql table model report.chicago_residential_parcel_sales_per_quarter_and_cpd_district [ERROR [0m in 7.44s]]
OK created sql table model report.chicago_residential_parcel_sales_per_quarter_and_cpd_beat [SELECT [0m in 7.54s]]
Finished running 2 view models, 21 table models in 0 hours 18 minutes and 45.97 seconds (1125.97s).
Completed with 1 error and 0 warnings:
Internal Error
Cache inconsistency detected: in rename, new key _ReferenceKey(database='re_dwh', schema='report', identifier='chicago_residential_parcel_sales_per_quarter_and_cp__dbt_backup') already in cache: [_ReferenceKeyschema='report', identifier='chicago_residential_parcel_sales_per_quarter_and_cpd_district'),
_ReferenceKey(schema='report', identifier='chicago_residential_parcel_sales_per_quarter_and_cp__dbt_backup')]
Name collisions can occur when the length of two models' names approach your database's builtin limit. Try restructuring your project such that no two models share the prefix 'chicago_residential_parcel_sales_per_quarter_and_cp'. Then, clean your warehouse of any removed models.
Done. PASS=22 WARN=0 ERROR=1 SKIP=0 TOTAL=23 Apparently postgres's default max identifier length is 63 bytes, and it seems dbt creates backup tables with the suffix In any case, I'll just make a note to limit table_names to 50 characters. |
This adds some clutter to the repo and I'd rather just generate reports via superset dashboards (which can be periodically updated and emailed or sent to slack per these instructions).
The text was updated successfully, but these errors were encountered: