Hi Lewis,
The stack traces you're seeing on the builds are caused by
https://issues.apache.org/jira/browse/CASSANDRA-4400
I have not seen such an exception on my environments, both on Linux
(CentOS) and Mac OSX.
Is it in gora-cassandra test console output, or in
target/surefire-reports/org.apache.gora.cassandra.store.TestCassandraStore.txt
?
What exactly is that exception ?
By the way, I tested Cassandra 1.0.0, 1.0.10, 1.1.0, and 1.1.2, and got
the same results as
https://issues.apache.org/jira/browse/GORA-53?focusedCommentId=13414694#comment-13414694
Regards,
-Kaz
On 7/18/12 11:22 AM, Lewis John Mcgibbney wrote:
Obviously the revert of cassandra-all to 1.1.0 didn;t help in this instance.
Does anyone know when this problem with cassandra-all kicked in? It
must have been before 1.1.0...
Lewis
On Wed, Jul 18, 2012 at 7:17 PM, Apache Jenkins Server
<[email protected]> wrote:
See
<https://builds.apache.org/job/gora-trunk/org.apache.gora$gora-cassandra/changes>
