<div dir="ltr">We should not embed Cassandra at all in that package. It would be confusing if there is a security issue in Cassandra.<div><div><br></div><div>Thomas</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 12:20 PM, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:jpkroehling@redhat.com" target="_blank">jpkroehling@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Team,<br>
<br>
As mentioned on IRC, we should not ship an embedded Cassandra with<br>
Hawkular Services. Here are a couple of approaches we can follow to<br>
accomplish that:<br>
<br>
- Keep everything as is, but change the default value for<br>
`hawkular.backend` to `remote` instead of the current `embedded_cassandra`<br>
<br>
- Remove the embedded Cassandra entirely from Nest. This has<br>
implications on how the integration tests are executed: we'd need to<br>
ensure that each integration test suite starts an embedded Cassandra<br>
before the test is executed. Or use an approach like Metrics, which<br>
requires Cassandra to be running before the tests are started.<br>
<br>
Which approach should be the one to follow?<br>
<br>
- Juca.<br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</blockquote></div><br></div>