Dear cassandra commiters and development process followers,
I would like to bring an important topic off build process of cassandra. I am
an external user from community point of view, however I been walking around
various projects close to cassandra over past year or even more. What is
worryin
Broadly as a contributor and operator I like the idea of more frequent
releases off of an always stable master. First customer ship quality
all the time [1]!
I'm a little concerned that the specific tick-tock proposal could
devolve into a 'devodd' style where the 'feature release' becomes a
I am trying to use Cassandra as a distributed systems infrastructure
component.
So it's gonna be embedded in Java processes to form a cluster and
queries will be executed by the wrapping process, not external clients.
On Tue, Mar 24, 2015 at 5:33 PM, Jack Krupansky
wrote:
> Are you trying to use
Are you trying to use Cassandra as a simple single-node data store within a
process, or are you trying to wrap Cassandra and run a cluster of custom
nodes? IOW, what are you trying to accomplish.
You could always run Cassandra as a spawned, background process, fully
controlled by a parent process.
Hi all,
As far as I understand it seems to be enough to initialize and activate
CassandraDaemon for embedding Cassandra. (Right?)
My question is what's the next step? Which class or classes should I use in
order to execute CQL queries for example?
Any pointers would be great.
Thanks!
--
Ersin
