this is the issue:
https://issues.apache.org/jira/browse/CASSANDRA-5383
guess it fell between chairs, will poke around
On Tue, Sep 24, 2013 at 4:26 PM, Nate McCall n...@thelastpickle.com wrote:
What version of 1.2.x?
Unfortunately, you must go through 1.2.9 first. See
and the new file name/content is used as
replacement.
From: Marcus Eriksson [mailto:krum...@gmail.com]
Sent: woensdag 25 september 2013 10:02
To: user@cassandra.apache.org
Subject: Re: Migration LCS from 1.2.X to 2.0.x exception
this is the issue:
https://issues.apache.org/jira/browse/CASSANDRA-5383
the rename in case of Windows could do the (scary) trick.
From: Desimpel, Ignace [mailto:ignace.desim...@nuance.com]
Sent: woensdag 25 september 2013 13:13
To: user@cassandra.apache.org
Subject: FW: Migration LCS from 1.2.X to 2.0.x exception
Same is true if started from 1.2.9 version to 2.0.x
Seems
Tested on WINDOWS : On startup of the 2.0.0 version from 1.2.x files I get an
error as listed below.
This is due to the code in LeveledManifest:: mutateLevel. The method already
has a comment saying that it is scary ...
On windows, one cannot use the File::rename if the target file name already
What version of 1.2.x?
Unfortunately, you must go through 1.2.9 first. See
https://github.com/apache/cassandra/blob/cassandra-2.0.0/NEWS.txt#L19-L24
On Tue, Sep 24, 2013 at 8:57 AM, Desimpel, Ignace
ignace.desim...@nuance.com wrote:
Tested on WINDOWS : On startup of the 2.0.0 version from
