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 <z...@uber.com> wrote: > > Seems the mail is marked as spam. So try forwarding with another email > account. > > Thanks, > Jay > > ---------- Forwarded message ---------- > From: Jay Zhuang <jay.zhu...@yahoo.com.invalid> > 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.org > > > 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 > the digest for the same schema is also changed: > https://github.com/apache/cassandra/blob/cassandra-3.0/src/ > java/org/apache/cassandra/schema/SchemaKeyspace.java#L311 > > I would suggest to have the older list back for digest calculation. But it > also means 3.0.13 -> 3.0.14 upgrade will have the same problem. Any > suggestion on that? > > Thanks, > Jay > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
