[
https://issues.apache.org/jira/browse/AIRFLOW-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175248#comment-17175248
]
ASF GitHub Bot commented on AIRFLOW-5644:
-----------------------------------------
BasPH commented on pull request #6317:
URL: https://github.com/apache/airflow/pull/6317#issuecomment-671732648
Setting DAG Run ids via the old TriggerDagRunOperator feels like one big
hack. Both from a code perspective (the Python callable to provide is odd to
read), and a logical perspective (I don't think it's desirable to have users
edit the run id).
To understand your use case, I'd like to know how exactly you're searching
for patient-specific DAG runs?
----------------------------------------------------------------
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)
