Re: [Hawkular-dev] Removal of embedded Cassandra
----- Mensaje original -----
De: "Juraci Paixão Kröhling"
<jpkroehling(a)redhat.com>
Para: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Enviados: Martes, 14 de Junio 2016 12:20:11
Asunto: [Hawkular-dev] Removal of embedded Cassandra
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?
Personally I prefer one that takes less steps to maintain our integration tests as they
are.
I'm not a fan of big refactoring just by this reason.
So, if we can solve these things with a variable better than change the whole nest and try
to package it again for itests.
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev