You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/04/29 16:02:04 UTC

[GitHub] [airflow] waleedsamy edited a comment on pull request #6317: [AIRFLOW-5644] Simplify TriggerDagRunOperator usage

waleedsamy edited a comment on pull request #6317:
URL: https://github.com/apache/airflow/pull/6317#issuecomment-829364149


   @BasPH 
   > 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?
   
   I don't think so, TriggerDagRunOperator should allow a user to set the RUN_ID the same way airflow cli allow the user to set run id using i.e `airflow dags trigger --run-id`.
   
   
   In my case, I use the TriggerDagRunOperator to trigger 30K dagrun daily and will be so annoying to see them having unidentifiable run_id.
   
   Could you please look into this again.
   


-- 
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:
users@infra.apache.org