afsalabdup commented on issue #9327:
URL: https://github.com/apache/airflow/issues/9327#issuecomment-1276441386
Thanks Bhavani for the explanation.
I think we can mark a future dag to success using execution Id. I mean run
cli command to mark whole dag to success and the moment that particular
schedule is hit, we will see all tasks in success state in UI. I think have
tested it and worked fine, please correct me if I am wrong.
Can we implement similar feature for tasks ?
At present, if I want to skip a task then someone should be available or
monitor closely the scheduled run to mark that task to success. This is
risk as job might start before we update it's state, since we can see that
instance only once that particular schedule is hit.
Regards,
Afsal
On Wed, Oct 12, 2022, 8:59 PM Bhavani Ravi ***@***.***> wrote:
> Hey Afsal,
>
> Dag Runs, and Task instances are created only when a particular schedule
> is hit.
> So with the current airflow design, there is no way to mark future task
> instances that haven't been created yet.
>
> But airflow tasks state command can be updated in such a way that
> downstream, upstream and task instances created after the current task
> instance can be marked success/failure
>
> This would replicate the behavior we have in the UI
> [image: image]
>
<https://user-images.githubusercontent.com/10116000/195384792-2839e212-4f59-4a36-b006-de32b7d35320.png>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/airflow/issues/9327#issuecomment-1276366458>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/AN6ATTEN2K6G3FRT2IRJJS3WC3KLXANCNFSM4N7QQ52A>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
