Some customers using the marketo__lead model have experienced a similar error to the one highlighted below. This is a result of the query using too many resources and timing out. Particularly the marekto__lead_calendar_spine is the model which fails.
This seems to only happen for customers who have a large dataset spanning a number of years. At the moment we have the marketo__first_date variable to allow users leveraging the dbt package to limit the data used in the package. However, this is not available for Quickstart users to adjust. Further the default value of that variable is the earliest lead date provided in the source data.
We will need to find a solution that allows Quickstart users and other users attempting to use this package to see success on an initial run. A few options include:
Change the default variable value to be the last year or so.
Adjust the underling model code to be more performant.
Consider restructuring the code to achieve the same results with less resources needed.
Relevant error log or model output
Query exceeded resource limits. This query used XXXXX CPU seconds but would only charge XXM Analysis bytes....
Expected behavior
All data models in this package are able to succeed without additional configuration. Especially for Quickstart users.
dbt Project configurations
n/a
Package versions
latest
What database are you using dbt with?
bigquery
dbt Version
latest
Additional Context
No response
Are you willing to open a PR to help address this issue?
[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
Is there an existing issue for this?
Describe the issue
Some customers using the
marketo__leadmodel have experienced a similar error to the one highlighted below. This is a result of the query using too many resources and timing out. Particularly themarekto__lead_calendar_spineis the model which fails.This seems to only happen for customers who have a large dataset spanning a number of years. At the moment we have the
marketo__first_datevariable to allow users leveraging the dbt package to limit the data used in the package. However, this is not available for Quickstart users to adjust. Further the default value of that variable is the earliest lead date provided in the source data.We will need to find a solution that allows Quickstart users and other users attempting to use this package to see success on an initial run. A few options include:
Relevant error log or model output
Expected behavior
All data models in this package are able to succeed without additional configuration. Especially for Quickstart users.
dbt Project configurations
n/a
Package versions
latest
What database are you using dbt with?
bigquery
dbt Version
latest
Additional Context
No response
Are you willing to open a PR to help address this issue?