Yes, the application includes the C* server and client.
From: Robert Stupp [mailto:sn...@snazy.de]
Sent: Wednesday, July 23, 2014 12:19 AM
To: user@cassandra.apache.org
Subject: Re: EXTERNAL: Re: Running Cassandra Server in an OSGi container
You mean "unzip and run" of an applicati
gt; Sent: Tuesday, July 22, 2014 1:19 PM
> To: user@cassandra.apache.org
> Subject: EXTERNAL: Re: Running Cassandra Server in an OSGi container
>
> What's your intention to do this?
>
> There are unit test integrations using C* daemon. A related bug that
>
"unzip and run" system and do not expect the user to have to
do much, if any, C* configuration.
From: Robert Stupp [mailto:sn...@snazy.de]
Sent: Tuesday, July 22, 2014 1:19 PM
To: user@cassandra.apache.org
Subject: EXTERNAL: Re: Running Cassandra Server in an OSGi container
What's yo
BTW, I agree with other posters that it seems like an awfully weird
thing to do. Perhaps you just want to run a client in an OSGI environment?
Jim C.
On 07/22/2014 02:39 PM, jcllings wrote:
> I can give you some tips.
>
> Figure out what Cassandra does when it starts up. Best way to do that
> is
I can give you some tips.
Figure out what Cassandra does when it starts up. Best way to do that is
to read the startup script. Then all you have to do is convince the
OSGI container to do what ever prep is done by the script. Trick to
that is usually figuring out where to do it. For example if t
What's your intention to do this?
There are unit test integrations using C* daemon. A related bug that prevented
proper shutdown has been closed for C* 2.1-rc1:
https://issues.apache.org/jira/browse/CASSANDRA-5635
It's perfectly fine to embed C* for unit tests.
But I'd definitely not recommend