[CASSANDRA-7697] UDF use new schema migration

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 2.2.0 beta 1
• Severity: Normal
• Assignee: Robert Stupp
• Reporter: Robert Stupp

Authors

Robert Stupp

• Created: 05/Aug/14 19:57
• Updated: 16/Apr/19 09:31
• Resolved: 05/Aug/14 23:13

Description

UDF is the "prototype candidate" for new, fine granular schema migration.

On the basic level, everything stays the same, more or less, except:

1. We might use separate versioning for migration messages (in addition to the messaging version)
2. 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.
3. Include the type of change with all other schema changes, for the same reason.
4. For schema pulls, use a merkle tree or something similar, to only pull/apply the relevant changes.

Issue Links

• is blocked by: CASSANDRA-6717 Modernize schema tables
• is related to: CASSANDRA-6038 Support schema changes in mixed version clusters
• is related to: CASSANDRA-7395 Support for pure user-defined functions (UDF)