I am using CCM to install the servers, it is bringing in the source code,
is there any option for CCM which I can set only to download the binary,
just to make sure it is not bringing in the working copy of the code.
I am using the following statements to create Keyspace and table definition.
create keyspace test1 with replication = { 'class':'SimpleStrategy',
'replication_factor':1};
CREATE TABLE IF NOT EXISTS wide (
time varchar,
name varchar,
value varchar,
PRIMARY KEY (time,name))
WITH COMPACT STORAGE;
On Fri, Feb 21, 2014 at 11:47 AM, Yogi Nerella <ynerella...@gmail.com>wrote:
> Sylvain,
>
> I am trying ccm to install and it does from source directory, I have tried
> 2.0.4/3/2/1 and 1.2.15, all of them are reporting the same failure after
> 127 records inserted.
>
> I am using 1.56.34 and 1.56.38 client both reports the same issue.
>
> Is something wrong with the client or the server, none of the server logs
> show any error.
>
> Thanks,
> Yogi
>
>
> On Wed, Feb 19, 2014 at 11:36 PM, Sylvain Lebresne
> <sylv...@datastax.com>wrote:
>
>>
>>
>>
>> On Wed, Feb 19, 2014 at 9:38 PM, Rüdiger Klaehn <rkla...@gmail.com>wrote:
>>
>>>
>>> I have cloned the cassandra repo, applied the patch, and built it. But
>>> when I want to run the bechmark I get an exception. See below. I tried with
>>> a non-managed dependency to
>>> cassandra-driver-core-2.0.0-rc3-SNAPSHOT-jar-with-dependencies.jar, which I
>>> compiled from source because I read that that might help. But that did not
>>> make a difference.
>>>
>>> So currently I don't know how to give the patch a try. Any ideas?
>>>
>>> cheers,
>>>
>>> Rüdiger
>>>
>>> Exception in thread "main" java.lang.IllegalArgumentException:
>>> replicate_on_write is not a column defined in this metadata
>>> at
>>> com.datastax.driver.core.ColumnDefinitions.getAllIdx(ColumnDefinitions.java:273)
>>> at
>>> com.datastax.driver.core.ColumnDefinitions.getFirstIdx(ColumnDefinitions.java:279)
>>> at com.datastax.driver.core.Row.getBool(Row.java:117)
>>> at
>>> com.datastax.driver.core.TableMetadata$Options.<init>(TableMetadata.java:474)
>>> at
>>> com.datastax.driver.core.TableMetadata.build(TableMetadata.java:107)
>>> at
>>> com.datastax.driver.core.Metadata.buildTableMetadata(Metadata.java:128)
>>> at com.datastax.driver.core.Metadata.rebuildSchema(Metadata.java:89)
>>> at
>>> com.datastax.driver.core.ControlConnection.refreshSchema(ControlConnection.java:259)
>>> at
>>> com.datastax.driver.core.ControlConnection.tryConnect(ControlConnection.java:214)
>>> at
>>> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:161)
>>> at
>>> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)
>>> at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:890)
>>> at
>>> com.datastax.driver.core.Cluster$Manager.newSession(Cluster.java:910)
>>> at
>>> com.datastax.driver.core.Cluster$Manager.access$200(Cluster.java:806)
>>> at com.datastax.driver.core.Cluster.connect(Cluster.java:158)
>>> at
>>> cassandra.CassandraTestMinimized$delayedInit$body.apply(CassandraTestMinimized.scala:31)
>>> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
>>> at
>>> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
>>> at scala.App$$anonfun$main$1.apply(App.scala:71)
>>> at scala.App$$anonfun$main$1.apply(App.scala:71)
>>> at scala.collection.immutable.List.foreach(List.scala:318)
>>> at
>>> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
>>> at scala.App$class.main(App.scala:71)
>>> at
>>> cassandra.CassandraTestMinimized$.main(CassandraTestMinimized.scala:5)
>>> at
>>> cassandra.CassandraTestMinimized.main(CassandraTestMinimized.scala)
>>>
>>
>> I believe you've tried the cassandra trunk branch? trunk is basically the
>> future Cassandra 2.1 and the driver is currently unhappy because the
>> replicate_on_write option has been removed in that version. I'm supposed to
>> have fixed that on the driver 2.0 branch like 2 days ago so maybe you're
>> also using a slightly old version of the driver sources in there? Or maybe
>> I've screwed up my fix, I'll double check. But anyway, it would be overall
>> simpler to test with the cassandra-2.0 branch of Cassandra, with which you
>> shouldn't run into that.
>>
>> --
>> Sylvain
>>
>
>
