Make Checksum-Update downwards compatible about liquibase HOT 5 OPEN

@robert-gdv - I have an update for you from the engineering team:

Liquibase now manages both the v8 and v9 checksum versions. Moving forward, this will not be a problem. If you need to revert back to a version before 4.24.0, then you will need to use clearChecksums.

from liquibase.

@kevin-atx : Thank you for your information. Although it is not totally clear. Are you informing me about a new feature or do you want to tell me how to solve the issue with the current system?

Downwards compatiblity was already working. AFAIK the checksums were simply updated to a newer version.
But is the current version upwards-compatible to a future v10 checksum?
Can v9 checksums be calculated and stored without deleting v8 checksums from the DB?
Will the roundtrip 4.20.0 -> 4.x.0 (x > 24) -> 4.20.0 require a manual operation on the DB?

My issue is that manual intervention with the DB is in production more costly to organize. Only very few have the permission to modify the DB. And because of the checksum-rewrite a liquibase minor version update requires a DB-Admin support.

from liquibase.

We are facing similar issue - spinnaker/spinnaker#6941
We upgraded liquibase from 3.10.3 to 4.24.0 in Spinnaker and started seeing errors like this - 8:f0bfebd55de9168e38a8ef9c7217c610 but is now: 8:d41d8cd98f00b204e9800998ecf8427e.
Manual overwriting of md5sum is not an option in production.

from liquibase.

@kirangodishala : You made quite a Version jump. This enhancement is about how different versions of checksums are stored.
When you seach the issues, you can find some entries where the same checksum version 8 was recalculated with a different result. e.g. #4156

from liquibase.

@robert-gdv - It's a big leap but we verified with the versions in between, and the checksum issue started with 4.23.0. Probably I need to raise a new issue then?

from liquibase.