> > > With TCM a schema change bumps an epoch, this epoch is then serialized with > every read command/partition update and the replica can check if it is > behind > or ahead of the coordinator. This allows the replica to either catch up > with > the coordinator before executing the read/write or fail the request if the > coordinator is behind. > OK. I understand that because the write's epoch is persisted this let's us order writes wrt relevant column drop correctly on the basis of epoch (not the timestamps like today - which doesn't work correctly).
-- Jakub Zytka e. jakub.zy...@datastax.com w. www.datastax.com
