Re: upgrading 1.1.x to 1.2.x via sstableloader

2013-04-05 Thread aaron morton
> Is it safe to change sstable file name to avoid name collisions? Yes. Make sure to change the generation number for all the components. Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 4/04/2013, at 3:01 PM, Micha

Re: upgrading 1.1.x to 1.2.x via sstableloader

2013-04-04 Thread Michał Czerwiński
I see, thanks for the replay! One more question: I can see that multiple nodes have same sstable names for a certain keyspace / cf. I am moving 8 nodes to a 6 nodes cluster, so at some point when putting sstables in place I would overwrite files from other node. What is the best way to solve this

Re: upgrading 1.1.x to 1.2.x via sstableloader

2013-04-03 Thread aaron morton
> java.lang.UnsupportedOperationException: SSTable zzz/xxx/yyy-hf-47-Data.db is > not compatible with current version ib You cannot stream files that have a different on disk format. 1.2 can read the old files, but cannot accept them as streams. You can copy the files to the new machines and us

upgrading 1.1.x to 1.2.x via sstableloader

2013-04-03 Thread Michał Czerwiński
Does anyone knows what is the best process to put data from cassandra 1.1.x (1.1.7 to be more precise) to cassandra 1.2.3 ? I am trying to use sstableloader and stream data to a new cluster but I get. ERROR [Thread-125] 2013-04-03 16:37:27,330 IncomingTcpConnection.java (line 183) Received stream