[
https://issues.apache.org/jira/browse/AIRFLOW-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175085#comment-17175085
]
ASF GitHub Bot commented on AIRFLOW-5644:
-----------------------------------------
ryanrichholt commented on pull request #6317:
URL: https://github.com/apache/airflow/pull/6317#issuecomment-671621332
@BasPH Could you clarify the reasoning that setting the run_id is abusing
the behavior? I'm working with Airflow to build DAGs that are externally
triggered once-per-patient, not on a time interval. It's very helpful to be
able to search the run_ids for a patient ID. So, each externally triggered DAG
run sets the run_id to a patient ID. I was hoping to be able to set the run_id
with this operator, but now it sounds like I'm going down the wrong path.
----------------------------------------------------------------
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)
