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 2022/03/02 06:31:19 UTC

[GitHub] [airflow] hterik commented on issue #21923: Programmatic customization of run_id for scheduled DagRuns

hterik commented on issue #21923:
URL: https://github.com/apache/airflow/issues/21923#issuecomment-1056360644


   Agree that navigating the UI based on dagrun-id is very confusing today. But i don't think generating custom `run_id` is necessarily the solution. 
   
   It would be better if the UI could format the id and even augment more data from the dagrun into a more meaningful description, for example reading parameters from the `conf` or reading output produced by selected `xcom` parameters. For most of our use cases the execution date itself means nothing, it is mostly the input provided via parameters that are used to identify a run.


-- 
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