kaxil commented on pull request #19637: URL: https://github.com/apache/airflow/pull/19637#issuecomment-972726885
>the messages the user sees are reassuring, and the system either self-heals or the user gets clear instructions what they should do I agree with this to add that instruction to run a deserialize command with "https://github.com/apache/airflow/blob/e25446a8b19197e55989174f210e1c94ae5ff65f/airflow/serialization/serialized_objects.py#L333"; And where we know we can take care of incompatibilities we can take care of them in migrations as suggested in https://github.com/apache/airflow/pull/19637#issuecomment-971897110 _I mean -- I don't think the "migration" / "cleanup" is needed then. If it was an oversight in 2.1.0 and we broke serialization, we will fix the deserialization part in 2.1.1 . Until now we didn't have to change the serialization format without breaking compatibility. When it comes to it, we can add a DB migration to fix those and do smart "migration" where only affected records are cleaned up._ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
