Thanks Erick, looks like I have a bit of detective work to do on Monday, to
work out which of my list of clusters started out as 2.* or DSE 4.* and whether
they had UDT’s at that time.
> On 15 Feb 2020, at 00:50, Erick Ramirez wrote:
>
> I am still having problems reproducing this, so I am wo
>
> I am still having problems reproducing this, so I am wondering if I have
> created the tables correctly to create this issue.
Paul, I've since had clarification on the bug and I hope I can explain it
correctly here (happy to be corrected if anyone else has insight on the
issue). When you crea
What does
http://cassandra.apache.org/doc/latest/tools/sstable/sstablemetadata.html show
as the type in the upgraded table? Also, the ticket mentions serialization
ordering being incorrect between single and multi-cell column data.
Perhaps there needs to be other non-PK fields to trigger this condi
Erick,
Thank you for your help.
I am still having problems reproducing this, so I am wondering if I have
created the tables correctly to create this issue.
I have looked at the sstabledumps and they seem exactly the same.
This is the pre upgrade version 3.0.14 ( a snapshotted version )
sstab
Paul, if you do a sstabledump in C* 3.0 (before upgrading) and compare it
to the dump output after upgrading to C* 3.11 then you will see that the
cell names in the outputs are different. This is the symptom of the broken
serialization header which leads to various exceptions during compactions
and
Hi all,
I have looked at the release notes for the up coming release 3.11.6 and seen
the part about corruption of frozen UDT types during upgrade from 3.0.
We have a number of cluster using UDT and have been upgrading to 3.11.4 and
haven’t noticed any problems.
In the ticket ( CASSANDRA-15035
