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
>
> 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
the scrub will be a no-op. Otherwise, it will
> report that new metadata files are being written. For more details, see
> https://support.datastax.com/hc/en-us/articles/360025955351. Cheers!
>
> Erick Ramirez | Developer Relations
> erick.rami...@datastax.com | datastax.com <http://w
Ramirez | Developer Relations
> erick.rami...@datastax.com <mailto:erick.rami...@datastax.com> | datastax.com
> <http://www.datastax.com/> <https://www.linkedin.com/company/datastax>
> <https://www.facebook.com/datastax> <https://twitter.com/datas
<https://github.com/datastax/>
<https://www.datastax.com/accelerate>
On Fri, 14 Feb 2020 at 01:43, Paul Chandler wrote:
> 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 fro
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
