mailto:jji...@gmail.com]
> Sent: Tuesday, August 1, 2017 5:13 PM
> To: cassandra <user@cassandra.apache.org>
> Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
>
> Roughly that approach should work, modulo copying data in/out to the right
> paths, and making sure you dont ov
legal/cri/index.html> for
Company Registration Information.
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, August 1, 2017 5:13 PM
To: cassandra <user@cassandra.apache.org>
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
Roughly that approach should work, modulo c
lick here
> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for
> Company Registration Information.
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com]
> *Sent:* Tuesday, August 1, 2017 3:36 PM
>
> *To:* user@cassandra.apache.org
> *Subject:*
t;
> From: Jeff Jirsa [mailto:jji...@gmail.com]
> Sent: Tuesday, August 1, 2017 3:36 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
>
> You can't stream across versions, so you either need to use the native
> protocol (do writes
i/index.html> for
Company Registration Information.
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, August 1, 2017 3:36 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
You can't stream across versions, so you either need to use the native proto
ed to receive for the recipient), please contact the sender by reply
> email and delete all copies of this message.
> Please click here for Company Registration Information.
>
> From: Jeff Jirsa [mailto:jji...@gmail.com]
> Sent: Tuesday, August 1, 2017 2:48 PM
> To: user@cas
2017 2:48 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
If you upgrade in place:
Stop each node one at a time
Swap binaries
Start each node
Run upgradesstables when all nodes are bounced
If you want to take data from 2.2 and put it into a 3.x cluster,
If you upgrade in place:
Stop each node one at a time
Swap binaries
Start each node
Run upgradesstables when all nodes are bounced
If you want to take data from 2.2 and put it into a 3.x cluster, you'll need to
run upgradesstables on it offline somehow (like clone that 2.2 cluster/schema
and
