Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Duplicate
    • Fix Version/s: 2.2.0 beta 1
    • Component/s: None
    • Labels:
      None
    • Severity:
      Normal

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                snazy Robert Stupp
                Reporter:
                snazy Robert Stupp
                Authors:
                Robert Stupp
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: