On 31 May 2017 at 03:41, Jeremiah D Jordan
wrote:
> If 3.0.13 causes schema mismatch on upgrade, then maybe we should pull
> that and release 3.0.14 once 13559 is fixed. As that is a pretty bad place
> to get into.
i think that would be a good idea
If 3.0.13 causes schema mismatch on upgrade, then maybe we should pull that and
release 3.0.14 once 13559 is fixed. As that is a pretty bad place to get into.
> On May 30, 2017, at 6:39 PM, Jay Zhuang wrote:
>
> Seems the mail is marked as spam. So try forwarding with another email
> account.
Seems the mail is marked as spam. So try forwarding with another email
account.
Thanks,
Jay
-- Forwarded message --
From: Jay Zhuang
Date: Tue, May 30, 2017 at 2:22 PM
Subject: Potential block issue for 3.0.13: schema version id mismatch while
upgrading
To: dev@cassandra.apache.o
Hi,
While upgrading to 3.0.13 we found that the schema id is changed for the
same schema. Which could cause cassandra unable to start and other
issues related to UnknownColumnFamilyException. Ticket: CASSANDRA-13559
The problem is because the order of SchemaKeyspace tables is changed.
Then t