I think the OP was asking if you can use the same Cassandra cluster
that Solandra
is integrated with to store non-Solandra in a different keyspace. This would
remove the need to run two Cassandra clusters, one for storing his Solandra
index, and another for his other data.
I'm not sure if Solandra
The best documentation (imo) for the Thrift API, is the cassandra.thrift
file in the 'interface' subdirectory of the releas. Because cassandra.thrift
is used to generate client bindings, it is always up to date, and usually
well commented. The wiki lags behind, but sometimes will have more details
Not sure, but I've been playing with running cassandra in the same VM as an
HTTP server for a pet project of mine, using a similar technique as the one
found in the Solandra project. It does use ports on localhost,
but hopefully gives you an idea of embedding cassandra (no clue if its a
good idea
