[GitHub] [airflow] turbaszek edited a comment on pull request #12312: Check for TaskGroup in _PythonDecoratedOperator

[GitBox <gi...@apache.org>]

turbaszek edited a comment on pull request #12312:
URL: https://github.com/apache/airflow/pull/12312#issuecomment-726697130


   > For example, if there are many `@task` decorated tasks without explicitly given `task_id`. Their task_ids will be generated sequentially: task__1, task__2, task__3, etc. After the DAG goes into production, one day someone inserts a new task before `task__2`. The task_ids after that will all be shifted forward by one place. This is going to produce `task__1, task__2, task__3, task__4`. But at this point the task__3 is no longer the same `task__3` as before. This is going to cause confusion when looking at historical DagRuns. E.g. history, log files, etc.
   
   This is a valid problem. I would be in favor of describing this in docs as I'm not sure if we will be able to solve this problem somehow (disabling id auto generation is rather no go for me).
   
   @casassg @kaxil @dimberman @ashb WDYT? 


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