[
https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-6695:
-----------------------------------------
Reproduced In: (was: 2.0.5)
Description:
Subject. Don't push schema to unknown-, or differently major-versioned nodes,
and don't pull schema from them, either.
Since we don't support schema altering during upgrade, and adding nodes during
cluster upgrades is also a non-recommended thing, this is what we are going to
do.
Until CASSANDRA-6038, that is.
was:
MigrationManager#announce() must not send schema to nodes it doesn't know the
version of, because they might be older ones.
Fix Version/s: 2.1
2.0.6
1.2.16
Assignee: Aleksey Yeschenko (was: Piotr Kołaczkowski)
Issue Type: Improvement (was: Bug)
Summary: Don't exchange schema between nodes with different versions
(no pull, no push) (was: Cassandra should not push schema updates to nodes
with unknown version)
Hijacking this issue to make broader changes, and apply them to 1.2 as well.
Also reclassifying this as an improvement, just because.
> Don't exchange schema between nodes with different versions (no pull, no push)
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-6695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6695
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Piotr Kołaczkowski
> Assignee: Aleksey Yeschenko
> Fix For: 1.2.16, 2.0.6, 2.1
>
> Attachments: 6695-v2.txt, 6695.patch
>
>
> Subject. Don't push schema to unknown-, or differently major-versioned nodes,
> and don't pull schema from them, either.
> Since we don't support schema altering during upgrade, and adding nodes
> during cluster upgrades is also a non-recommended thing, this is what we are
> going to do.
> Until CASSANDRA-6038, that is.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
