mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-21 17:10:35 +00:00
88ba184247
Try to look up and use schema from the local schema_registry in case when we have a schema mismatch between the most recent schema version and the one that is stored inside the `frozen_mutation` for the accepted proposal. When such situation happens the stored `frozen_mutation` is able to be applied only if we are lucky enough and column_mapping in the mutation is "compatible" with the new table schema. It wouldn't work if, for example, the columns are reordered, or some columns, which are referenced by an LWT query, are dropped. With the patch we are able to mitigate these cases as long as the referenced schema is still present in the node cache (e.g. it didn't restart/crash or the cache entry is not too old to be evicted). Tests: unit(dev, debug), dtest(paxos_tests.schema_mismatch_*_test) Signed-off-by: Pavel Solodovnikov <pa.solodovnikov@scylladb.com> Message-Id: <20200827150844.624017-1-pa.solodovnikov@scylladb.com>