-
Notifications
You must be signed in to change notification settings - Fork 728
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
GCP Integration #22
Comments
@manesioz Curious, what does your tech stack look like on GCP? Kubernetes +GCS + Airflow? |
We actually run Airflow on Cloud Composer, and our data lake is in BigQuery. We're currently considering migrating to Kubernetes |
Got it. We have a similar issue open at #16. |
At Mailchimp, we also use Cloud Dataflow. We could potentially contribute to the effort to support GCP. In particular, we have a battle-tested We would be happy to share this code for inclusion in Metaflow. Our decoraor incorporates a fork of the Apache 2.0 licensed
|
@barrywhart We would be happy to engage on a POC. @jaychia already has a PR out for GCS integration. |
@savingoyal: We are not currently using Metaflow, but I see some potential for using it in some cases as an alternate to Airflow (complex!) and bash scripts (may not always be powerful enough for our needs). So I want to help, but also need to time box my involvement for now. Can you point me to the GCS PR? Any thoughts on how the package might accomodate multiple |
#153 - please feel free to contribute or comment The Metaflow S3 datastore internally does its own error handling for storage-client-related retries (retry N number of times if an error that isn't metaflow-related is thrown). I replicated that logic for the GCS datastore. See: Also, tenacity is a great retrying package that should be able to do the custom retry logic that you mentioned (wait period depends on type of error). |
Is PR #153 still relevant? |
First of all, thank you for open-sourcing this excellent tool!
My team uses GCP not AWS so if
metaflow
could be integrated that would be great. I'm sure its on your roadmap but just putting it out there :)The text was updated successfully, but these errors were encountered: