[
https://issues.apache.org/jira/browse/AIRFLOW-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175840#comment-17175840
]
ASF GitHub Bot commented on AIRFLOW-5644:
-----------------------------------------
ryanrichholt commented on pull request #6317:
URL: https://github.com/apache/airflow/pull/6317#issuecomment-672277149
In the DagRun model list view there is an option to search by run_id. Since
we set the run_id when the dag is triggered externally, this field can be used
when we need to check on progress for a specific case.
This seems to work alright, but there are some downsides:
- run_id doesn't propagate to subdags, so we basically cant use subdags
- run_id can't be set when triggering the dag from some of the quick buttons
in the ui
- with the create dag_run form, the run_id can be set, but the conf cannot
So, I'm also exploring options for moving away from using run_ids, and just
adding this info to the run conf. But, I think this is going to require
updating the DagRun model views, or a custom view plugin.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> Simplify TriggerDagRunOperator usage
> ------------------------------------
>
> Key: AIRFLOW-5644
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5644
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 2.0.0
> Reporter: Bas Harenslak
> Priority: Major
> Fix For: 2.0.0
>
>
> The TriggerDagRunOperator usage is rather odd at the moment, especially the
> way to pass a conf.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
