Re: Restore a table with dropped columns to a new cluster fails

2020-07-24 Thread Mitch Gitman
Fabulous tip. Thanks, Sean. I will definitely check out dsbulk. Great to see it's a Cassandra-general tool and not just limited to DataStax Enterprise. On Fri, Jul 24, 2020 at 12:58 PM Durity, Sean R wrote: > I would use dsbulk to unload and load. Then the schemas don’t really > matter. You def

[RELEASE] Apache Cassandra 3.11.7 released

2020-07-24 Thread Mick Semb Wever
The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.7. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

[RELEASE] Apache Cassandra 2.2.17 released

2020-07-24 Thread Mick Semb Wever
The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.17. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

RE: Restore a table with dropped columns to a new cluster fails

2020-07-24 Thread Durity, Sean R
I would use dsbulk to unload and load. Then the schemas don’t really matter. You define which fields in the resulting file are loaded into which columns. You also won’t have the limitations and slowness of COPY TO/FROM. Sean Durity From: Mitch Gitman Sent: Friday, July 24, 2020 2:22 PM To: us

Re: Restore a table with dropped columns to a new cluster fails

2020-07-24 Thread Mitch Gitman
I'm reviving this thread because I'm looking for a non-hacky way to migrate data from one cluster to another using nodetool snapshot and sstableloader without having to preserve dropped columns in the new schema. In my view, that's just cruft and confusion that keeps building. The best idea I can

Re: [RELEASE] Apache Cassandra 4.0-beta1 released

2020-07-24 Thread Mick Semb Wever
> This version is a beta release[1] on the 4.0 series. As always, please > pay attention to the release notes[2] and let us know[3] if you were > to encounter any problem. A quick followup note to both user and dev groups. Our Beta release guidelines¹ states that there will be no further API ch