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/11/17 17:02:35 UTC

[GitHub] [airflow] kaxil edited a comment on pull request #19637: Trigger DAG re-serialization after upgrade

kaxil edited a comment on pull request #19637:
URL: https://github.com/apache/airflow/pull/19637#issuecomment-971775593


   > I am also +1 on doing it always.
   
   
   Agree when we have incompatibilities -- and we can resync during that version is what I feel.
   
   > 
   > I prefer even 10 minutes of resync (which is I guess highly unrealistic to take that long on pretty much any upgrade) for every user at upgrade time than handling all the issues that people will have in case of any future incompatibilities/migration from older versions.
   
   It compounds to 30 mins -- when you account for other DB migrations. The larger the number of DAGs, larger the TIs, more time for other migrations and more time for re-serialization 


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