[Hawkular-dev] Manage cassandra-all in hawkular-parent

[Lucas Ponce]

Related with C* 2.2.0, I've found an small issue in the EmbeddedCassandraService.

I've sent a PR here:

https://github.com/hawkular/hawkular-commons/pull/14


I've tested using the hawkular-alerts -Pstandalone developer profile and I could reproduce the issue and check the fix.

Lucas

----- Original Message -----
> From: "John Sanda" <jsanda at redhat.com>
> To: "Peter Palaga" <ppalaga at redhat.com>
> Cc: hawkular-dev at lists.jboss.org
> Sent: Friday, August 14, 2015 4:39:26 PM
> Subject: Re: [Hawkular-dev] Manage cassandra-all in hawkular-parent
> 
> 
> 
> 
> 
> On Aug 14, 2015, at 6:50 AM, Peter Palaga < ppalaga at redhat.com > wrote:
> 
> Hi John,
> 
> thanks to Lukáš's expertise, we now know that the named stacktrace is
> Cassandra's internal problem. Their cassandra-all:2.2.0 artifact by mistake
> depends on thrift-server 0.3.5 which should correctly be 0.3.7.
> 
> Lukáš reported the problem in their Jira:
> https://issues.apache.org/jira/browse/CASSANDRA-10071 and I attached a
> patch.
> 
> Question 1: I do not know how deeply you are engaged in the c* community, but
> you may perhaps help somehow to speedup the process by reviewing/merging the
> patch and after that proposing a new 2.2.* release?
> 
> Unfortunately there is nothing I can offer. We need to be aware of the
> planned release schedule changes described in
> http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/ . C* 3.0
> is planned for September, and once it is out 2.1 will reach end of like
> which I assume means no more releases. 2.2 will be maintained until 4.0 is
> out, which should be another year. This is particularly important for
> inventory because Titan depends on Thrift and I think Thrift is being
> removed in 3.0.
> 
> 
> 
> 
> 
> Question 2: Independently from how fast can the issue be resolved in
> upstream, there is a workaround possible in embedded-cassandra:
> https://github.com/ppalaga/hawkular-commons/commit/25450efedab347d3064d1093da3b22e5c03160b3
> I have just tested with c* 2.2.0 and at least the integration tests in
> hawkular have all passed. I'd release embedded-cassandra with this
> workaround so that we are on 2.2.* unless you raise some concerns?
> 
> Thanks,
> 
> Looks fine to me. Thanks for investigating.
> 
> 
>