cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7697) UDF use new schema migration
Date Tue, 05 Aug 2014 23:15:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-7697.
------------------------------------------

    Resolution: Duplicate

> UDF use new schema migration
> ----------------------------
>
>                 Key: CASSANDRA-7697
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7697
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>             Fix For: 3.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message