This fixes the problem where the cordinator already knows about the new schema and issues a read which uses new objects, but the replica doesn't know those objects yet. The read will fail in this case. We can avoid this if we propagate schema changes with reads, like we already do for writes. Message-Id: <20210205163422.414275-1-tgrabiec@scylladb.com>