You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There recently was an update to the Apple Store schema which this data model does not currently support. We need to explore the new schema and plan to migrate the current data model to support the newer schema provided by the connector.
Relevant error log or model output
Models will fail as they search fortables that don't existin the new schema.
Expected behavior
The model works on the new schema and recreates to the best of the ability the original end models built using the old schema. Also, it's essential this works with the downstream App Reporting package.
Possible solution
Reference the new schema and redesign the Apple Store source and transform package to rebuild the same end models given the new source tables.
Is there an existing issue for this?
Describe the issue
There recently was an update to the Apple Store schema which this data model does not currently support. We need to explore the new schema and plan to migrate the current data model to support the newer schema provided by the connector.
Relevant error log or model output
Expected behavior
The model works on the new schema and recreates to the best of the ability the original end models built using the old schema. Also, it's essential this works with the downstream App Reporting package.
Possible solution
Reference the new schema and redesign the Apple Store source and transform package to rebuild the same end models given the new source tables.
dbt Project configurations
Default
Package versions
Latest
What database are you using dbt with?
postgres, redshift, snowflake, bigquery, databricks
How are you running this dbt package?
Fivetran Quickstart Data Model, Fivetran Transformations, dbt Core™, dbt Cloud™
dbt Version
Latest
Additional Context
No response
Are you willing to open a PR to help address this issue?
The text was updated successfully, but these errors were encountered: