[Hawkular-dev] Removal of embedded Cassandra

[Thomas Heute]

We should not embed Cassandra at all in that package. It would be confusing
if there is a security issue in Cassandra.

Thomas

On Tue, Jun 14, 2016 at 12:20 PM, Juraci Paixão Kröhling <
jpkroehling at redhat.com> wrote:

> Team,
>
> As mentioned on IRC, we should not ship an embedded Cassandra with
> Hawkular Services. Here are a couple of approaches we can follow to
> accomplish that:
>
> - Keep everything as is, but change the default value for
> `hawkular.backend` to `remote` instead of the current `embedded_cassandra`
>
> - Remove the embedded Cassandra entirely from Nest. This has
> implications on how the integration tests are executed: we'd need to
> ensure that each integration test suite starts an embedded Cassandra
> before the test is executed. Or use an approach like Metrics, which
> requires Cassandra to be running before the tests are started.
>
> Which approach should be the one to follow?
>
> - Juca.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/4700d843/attachment.html