Hi,
Thanks for your replay.
I was starting to suspect something like this, by your description there
dosen't seam to be a straight forward fix for the issue, if it can be fixed at
all in a good way.
For me this was a really minor issue, it was just in a test case that I could
rewrite so I did
It looks like there are a couple of things going on here. The type check
when adding a UDT column:
new_type.isValueCompatibleWith(dropped_type)
will only be true if the dropped type is a UDT. This however will never be
the case, since UDT types are replaced with tuple when converted to a
dropped
I have seen this situation causing corruption due to different structure but
same name column in old and new sstables.
Regards,
Nitan
Cell: 510 449 9629
> On Nov 21, 2019, at 7:59 AM, Tommy Stendahl
> wrote:
>
>
> Hi,
>
> I run in to problem with 3.11.5, I think its related to "* Toughen
Hi,
I run in to problem with 3.11.5, I think its related to "* Toughen up column
drop/recreate type validations (CASSANDRA-15204)"
I have a user defined type and I have a table with a column that has this UDF
as type, if I drop the column and recreate it with the same name it fails. I
think th
