You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2023/04/26 16:42:17 UTC

[GitHub] [airflow] potiuk commented on issue #30869: Airflow REST API: Support getting information about cross-dag dependencies via GET request

potiuk commented on issue #30869:
URL: https://github.com/apache/airflow/issues/30869#issuecomment-1523737075

   I think what you are really looking at are Dataset support. TriggerDagRun is just an operator and we are not planning to add more semantics meaning and make specific API for that. From the point of view this is  specific operator "trigger DAGrun" that has speicific parameters (dag_id to trigger) and if you want to parse it and build your dependencies there, you are free to do so.
   
   But really the way we added (and we plan to build on) when it comes to dag dependencies is dataset-driven schedule and dataset dependencies and it has not only capabilities of keeping relations between dags and tasks, but also add semantic meaning to the dataset produced and consumed by those, and it will be acompanied with Lineage information as well.  So you almost definiely want to use datasets for what you want to do https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/get_dataset
   
   Converting it to a discussion - this is of course my personal view, but it is highly unlikely we are going to enhance generic DAG/TASK API with more semantics information about the dependencies, where Datasets are the future.
   
   Converting it to a discussion if more of it is needed.
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org