-
Notifications
You must be signed in to change notification settings - Fork 14
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
Enable dbt python models via serverless Dataproc and create example model #2346
Conversation
a07e455
to
e817268
Compare
Warehouse report 📦 New models 🌱mart.gtfs.dim_shapes_arrays_enriched Changed models 🔀mart.gtfs_quality.fct_daily_organization_combined_guideline_checks DAG |
2a78017
to
27a4422
Compare
1c52ba8
to
802ea8d
Compare
802ea8d
to
892f2f1
Compare
7c575da
to
ef4047d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still waiting on dbt-labs/dbt-bigquery#636 but we can fork if necessary
Is this actually a blocker to merge?
Would it be useful to add some documentation about this functionality to the warehouse README? Are there any links we could add about where to check if you need to troubleshoot any of this setup?
No, but developer experience will be poor; I gave this caveat to tiffany and eric in our tech spec meeting yesterday. I've added some other documentation! |
Description
I had to enable Google Private Access on our default VPC, and also grant access in the prod project (BigQuery and GCS) to the staging default compute service account since local dbt runs use the staging project.
Still waiting on dbt-labs/dbt-bigquery#636 but we can fork if necessary
Blocked on dbt-labs/dbt-bigquery#609We had a meeting today (2023-05-31) to review the tech spec, so I'd like to merge this ahead of a to-be-scheduled pairing session to test an initial model.
Type of change
How has this been tested?
I had created and tested an example model, but we don't actually want/need it. Pasting the source code here for posterity; it ran on our custom image provided to Dataproc.
Screenshots (optional)