This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
generated from astronomer/astro-providers-template
-
Notifications
You must be signed in to change notification settings - Fork 11
New Feature Request: Handling retry at the notebook level #65
Comments
Hi, @RafaelCartenet, this is a handy feature. |
Hey Tatiana
I could eventually, could you please let me know what it takes to
contribute ?
Also I'm curious about the current status of this project. It's really
promising though it doesn't look like being updated really often. Is
Astronomer still looking into maintaining it long term ?
Best
Rafael
…On Thu, May 9, 2024 at 10:29 PM Tatiana Al-Chueyr ***@***.***> wrote:
Hi, @RafaelCartenet <https://github.com/RafaelCartenet>, this is a handy
feature.
We could also have this associated with the Airflow task retry, so Airflow
could automatically retry tasks on failure.
Would you be interested in contributing to the project?
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXKHJRZYWF5MMDSFE26EHDZBOB6NAVCNFSM6AAAAABERXUJPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSG43TOMZSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @RafaelCartenet ! Those are great questions. Astronomer is contributing this provider to the Apache Airflow Databricks provider so it can be part of a larger community - both users and contributors. These are the steps:
I see the feature you requested being developed / contributed after the migration. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey, been using the library for a while now, love it, thanks for the good work.
Trying to implement retry at the notebook level, Databricks have parameters for it you can change in the UI that appear like this in the json:
I'm unable to set those parameters with astro_databricks
Thanks in advance
The text was updated successfully, but these errors were encountered: