Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to 3.5 as well, and it makes Cassandra effectively unusable if someone is using any of the 4 types affected in any of their schema.
I have cherry picked & merged the patch back to here and will put it in a JIRA as well tonight, I just wanted to get the ball rolling asap on this. https://github.com/rustyrazorblade/cassandra/tree/fix_commitlog_exception Jon
