> >
> > I'll note that while far from idea, you can also disable assertion with
> 2.0.3.
>
> Is there a way to do that without patching/recompiling?? You make it sound
> as if there is...
>
>
Comment the following line in cassandra-env.sh:
JVM_OPTS="$JVM_OPTS -ea"
On 19.12.2013, at 14:09, Sylvain Lebresne wrote:
>
>
> Is there anything I can do except waiting for a fix?
>
> Disable paging (which might imply having to do some manual paging if the
> result set you were querying were really big).
Yes, that was my original code - might do that.
>
> I'
>
> Is there anything I can do except waiting for a fix?
>
Disable paging (which might imply having to do some manual paging if the
result set you were querying were really big).
>
> I moved to 2.0.3 because I think I experienced missing rows in 2.0.1
> paging - is this related to the 2.0.3 bug?
Sylvain,
thanks.
Is there anything I can do except waiting for a fix?
Could I do something to my data? Or data model?
I moved to 2.0.3 because I think I experienced missing rows in 2.0.1 paging -
is this related to the 2.0.3 bug? Meaning: going back to 2.0.1 will fix the
exception, but leave
https://issues.apache.org/jira/browse/CASSANDRA-6447
On Thu, Dec 19, 2013 at 11:16 AM, Jan Algermissen <
jan.algermis...@nordsc.com> wrote:
> Hi all,
>
> after upgrading C* and the java-driver I am running into problems with
> paging. Maybe someone can provide a quick clue.
>
> Upgrading was
>
Hi all,
after upgrading C* and the java-driver I am running into problems with paging.
Maybe someone can provide a quick clue.
Upgrading was
C* from 2.0.1 to 2.0.3
Java Driver from 2.0.0-rc1 to 2.0.0-rc2
Client side, I get the following messages (apparently during a call to
resultSet.on
