Sorry my advice is not good for you, if you are moving to another platform with a different portionner, i think sstableloader is the right tool for you.
http://www.datastax.com/docs/1.1/references/bulkloader http://www.datastax.com/dev/blog/bulk-loading 2014-07-30 10:51 GMT+02:00 Hao Cheng <br...@critica.io>: > No idea if this will help, but have you tried the sstable2json and > json2sstable utilities to output json from your old cluster and import it > into the new one? > > > On Wed, Jul 30, 2014 at 1:40 AM, Kais Ahmed <k...@neteck-fr.com> wrote: > >> hi tsi, >> >> You have you upgrade to 1.2.9 first. >> >> 2.0.0 >> ===== >> >> Upgrading >> --------- >> >> - Java 7 is now *required*! >> - Upgrading is ONLY supported from Cassandra 1.2.9 or later. This >> >> goes for sstable compatibility as well as network. When >> upgrading from an earlier release, upgrade to 1.2.9 first and >> >> >> run upgradesstables before proceeding to 2.0. >> >> >> >> 2014-07-30 8:51 GMT+02:00 Paco Trujillo <f.truji...@genetwister.nl>: >> >> Hi tsi >>> >>> We faced a similar situation a few months ago. At the end what we make >>> is developed a service in our application to migrate the data from the old >>> cassandra 1.2 to the new cassandra 2.0 using cql (with normal SELECT and >>> UPDATE commands) (our application at that moment have two cassandra >>> sessions, one for the 1.2 and another for the 2.0) . I know it is not the >>> perfect solution but by this way we could migrate the data without >>> considering anything about partitioner >>> >>> Kind regards >>> >>> >>> >>> ------------------------------------------------------------------------------------ >>> Francisco Trujillo - BioInformatic Developer >>> >>> Genetwister Technologies B.V. >>> >>> Phone: +31 317 466420 >>> Fax: +31 317 466421 >>> Email:f.truji...@genetwister.nl >>> Internet:www.genetwister.nl >>> >>> -------------------------------------------------------------------------------------- >>> Disclaimer >>> This e-mail and any files transmitted with it are confidential and >>> intended solely for the use of the individual or entity to whom/which they >>> are addressed. If you have received this e-mail in error please notify the >>> sender immediately, delete this e-mail from your system and do not >>> disseminate, distribute or copy this e-mail. This e-mail shall not >>> constitute a binding agreement unless expressly confirmed in writing by one >>> of the Directors of Genetwister. Please note that any views or opinions >>> presented in this e-mail are solely those of the author and do not >>> necessarily represent those of Genetwister. Finally, the recipient should >>> check this e-mail and any attachments for the presence of viruses. >>> Genetwister accepts no liability for any damage caused by any virus >>> transmitted by this e-mail or damage caused by the use of the information >>> contained in this e-mail. >>> ________________________________________ >>> From: tsi [thorsten.s...@t-systems.com] >>> Sent: Tuesday, July 29, 2014 2:53 PM >>> To: cassandra-u...@incubator.apache.org >>> Subject: Re: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with >>> changed partitioner settings >>> >>> We are moving our application to a plattform with this partitioner >>> setting >>> and as far as I know there is no way to specify a partitioner on keyspace >>> level. >>> >>> >>> >>> -- >>> View this message in context: >>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Migration-from-Cassandra-1-2-5-to-Cassandra-2-0-8-with-changed-partitioner-settings-tp7596019p7596021.html >>> Sent from the cassandra-u...@incubator.apache.org mailing list archive >>> at Nabble.com. >>> >> >> >
