potiuk commented on pull request #9276:
URL: https://github.com/apache/airflow/pull/9276#issuecomment-644084786
> If we don't give users the ability to test changes without jumping
straight to 2.0 then a lot of bigger companies are going to be very reluctant
to upgrade. (It's hard enough to get them to upgrade minor Airflow versions.)
Absolutely all those scenarios should include testing. But I think there
will be many companies that will not like to make two migrations - 1.10.x
whatever they have now - 1.10.12 -> 2.0.0., they would rather migrate to 2.0
straight. Of course, we might choose to not support this path - as community.
But I do not think it should be taken as granted without discussion and hearing
the user's opinion on that.
> > I do not know what are the plans, for now, I do not know if it's been
discussed - the migrations are long time separated between the databases in
1.10 and 2.0 so I am not sure if there is a clear path (yet) on how to migrate
from a version of 1.10 to 2.0.
>
> It is a hard requirement that it is possible to update DB from 1.10 to
2.0. Resetting the DB means a very likely chance that Airflow would then go and
re-run months or years worth of tasks.
I agree "clean-cut' might not be the best way of doing it, yet I imagine
scenarios where this might be the path taken by our users. I think it's worth
starting the discussion on the devlist a least, as this might be a viable
option for some of the customers (no capacity for that from my side though
currently).
I do not think we had an opportunity to migrate the "major" largely
backwards in-compatible version yet, so hearing what the users think about this
might be a good way to make good decisions on it.
----------------------------------------------------------------
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:
[email protected]
