That was exactly the problem, thx. (I'm starting a new thread to chat
about it)
On 10/11/11 6:31 AM, "Sylvain Lebresne" wrote:
>@Todd You're likely doing something wrong with your ByteBuffers. It's
>*very* easy
>to screw up with those.
>
>--
>Sylvain
>
>On Tue, Oct 11, 2011 at 7:30 AM, Todd Bur
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
>
+1
On Tue, Oct 11, 2011 at 8:32 AM, Brandon Williams wrote:
> On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne
> wrote:
>> So I have created new artifacts, based on the previous ones but with the
>> infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And what I'm
>> proposing is to simply
On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne wrote:
> So I have created new artifacts, based on the previous ones but with the
> infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And what I'm
> proposing is to simply switch to those last artifacts for the release instead
> of the initi
@Todd You're likely doing something wrong with your ByteBuffers. It's
*very* easy
to screw up with those.
--
Sylvain
On Tue, Oct 11, 2011 at 7:30 AM, Todd Burruss wrote:
> This is a bit preliminary, but wanted to get this to you guys knowing the
> vote is in progress
>
> using these artifac
The artifacts for this vote happen to have
https://issues.apache.org/jira/browse/CASSANDRA-3343.
This is a purely cosmetic issue, and clearly I don't want to reroll the vote
for this, which would delay the release.
But I also think that fixing this issue has zero chance of screwing anything
up, s
This is a bit preliminary, but wanted to get this to you guys knowing the
vote is in progress
using these artifacts I am seeing the following exception on restart.
(also with RC1 and RC2.) the only interesting tidbit is that it seems to
only happen when writing via direct calls to StoragePro
+1
On Mon, Oct 10, 2011 at 12:24 PM, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough
> to
> warrant a reroll. So here it is: I propose the following artifacts for
> release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
>
+1 (non-binding)
-Stephen
On 10 October 2011 17:24, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch f
+1
On Mon, Oct 10, 2011 at 11:24, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
>
+1
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-333
As said while closing previous vote, CASSANDRA-3338 felt important enough to
warrant a reroll. So here it is: I propose the following artifacts for release
as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
and a one line fix to the build file so that it picks the right ver
13 matches
Mail list logo
