Re: Starting up cassandra 0.7

Bryan added a patch. Can someone please review? Thanks. On Wed, Nov 17, 2010 at 12:10 PM, CassUser CassUser wrote: > We are putting together a patch for that. Also updating the unit test to > capture this case. It wasn't failing as a result of it being backwards. > > > On Wed, Nov 17, 2010 at

Re: Starting up cassandra 0.7

We are putting together a patch for that. Also updating the unit test to capture this case. It wasn't failing as a result of it being backwards. On Wed, Nov 17, 2010 at 11:51 AM, CassUser CassUser wrote: > Thanks for looking into that. I created a jira issue for it: > > https://issues.apache.or

Re: Starting up cassandra 0.7

Thanks for looking into that. I created a jira issue for it: https://issues.apache.org/jira/browse/CASSANDRA-1753 On Wed, Nov 17, 2010 at 11:28 AM, Aaron Morton wrote: > That does look like a bug > http://www.mail-archive.com/d...@cassandra.apache.org/msg01167.html > >

Re: Starting up cassandra 0.7

That does look like a bug http://www.mail-archive.com/d...@cassandra.apache.org/msg01167.htmlAaronOn 17 Nov, 2010,at 03:55 PM, Aaron Morton wrote:It's certainly looks suspect. I've had a look at the code around SSTableImport and SSTableExport and the isDeleted value for the col is based on IColumn

Re: Starting up cassandra 0.7

It's certainly looks suspect. I've had a look at the code around SSTableImport and SSTableExport and the isDeleted value for the col is based on IColumn.isMarkedForDelete read when the data was exported. I'll try to have a look tonight, or if someone is still up in the states they may help. The cur

Re: Starting up cassandra 0.7

Looking at this closer. I noticed the following in the SSTableImport Class: if (col.isDeleted) { cfamily.addColumn(path, hexToBytes(col.value), new TimestampClock(col.timestamp)); } else { cfamily.addTombstone(path, hexToBytes(col.value), ne

Re: Starting up cassandra 0.7

Looked at how DatabaseDescriptor is loading the yaml file. Using that approach solves the problem with the column_families mapping exception. The problems we are running into currently is regarding a known dataset not being loaded into our test instance correctly. Steps: 1. Create temp director

Re: Starting up cassandra 0.7

I've not used the embedded service. The code in o.a.c.service.EmbeddedCassandraService says it will read the yaml file. If the cluster does not have a schema stored I think it will load the one from yaml. Have you tried starting it up with an empty system data dir ? Does it pickup the schema from t

Re: Starting up cassandra 0.7

Loading yaml file like so: FileInputStream yamlInputStream = new FileInputStream( configTemplateFile); Constructor constructor = new Constructor(Config.class); Yaml yaml = new Yaml(new Loader(constructor)); Config conf = (Config) yaml.load(yamlInputSt

Re: Starting up cassandra 0.7

This is embedded for testing cassandra 0.7 beta2. using EmbeddedCassandraService. and manually adding schema programmatically using: for (KSMetaData table : DatabaseDescriptor.readTablesFromYaml()) { for (CFMetaData cfm : table.cfMetaData().values()) { CFMetaDa

Re: Starting up cassandra 0.7

AFAIK the ArrayStoreException is similar to a type mismatch. Is it possible you have something mixed up in your class path or source code if you built from source? It looks like the column family info was deserialised into a o.a.c.config.RawColumnFamily but when that object was added to the RawColu

Starting up cassandra 0.7

Here is the yaml: # Cassandra YAML generated from previous config # Configuration wiki: http://wiki.apache.org/cassandra/StorageConfiguration authenticator: org.apache.cassandra.auth.AllowAllAuthenticator auto_bootstrap: false binary_memtable_throughput_in_mb: 256 cluster_name: Test Cluster column