dzpan0 commented on PR #67832:
URL: https://github.com/apache/airflow/pull/67832#issuecomment-4671855470
> `GET /dags/{dag_id}/tasks/existence`
>
> That should be some kind of HEAD request I think.
>
> But more importantly, I don't know why we need a separate request for
this. We make a normal request to get the task status don't we? So couldn't we
make a 404 from the get status request encode that info already?
I thought making the endpoint separate the given tasks into two lists would
allow more liberty and diverse use cases than just checking weather the tasks
exist.
On the other note, I thought using `get_task_states` could be ambiguous when
a Dag has no DagRuns.
> > Existing dag-level Execution API routes can't distinguish a Dag that
doesn't exist from a Dag that exists, but has no DagRuns
>
> Dag Versioning makes this problematic. Until a run exists, there is no
gurantee that the task will exist in any given run.
Yeah, that makes sense. I'll close this for now and have another think about
it.
Thanks.
--
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]
