Fix Version/s: 2.2.0 beta 1
UDF is the "prototype candidate" for new, fine granular schema migration.
On the basic level, everything stays the same, more or less, except:
- We might use separate versioning for migration messages (in addition to the messaging version)
- For DROP X changes, we only encode what's necessary (the keyspace name, the table name, the timestamp). Not to save bytes, but to avoid going through a full schema merge on the node.
- Include the type of change with all other schema changes, for the same reason.
- For schema pulls, use a merkle tree or something similar, to only pull/apply the relevant changes.