Is it really like that? Where does this info come from? I haven’t seen anything “official" yet.
Hannu > On 26 Jan 2016, at 15:07, <sean_r_dur...@homedepot.com> > <sean_r_dur...@homedepot.com> wrote: > > This is a very strange move considering how well DataStax has supported open > source Cassandra. I hope there is a reasonable and well-publicized > explanation for this apparent change in direction. > > > Sean Durity > > From: George Sigletos [mailto:sigle...@textkernel.nl] > Sent: Tuesday, January 26, 2016 4:09 AM > To: user@cassandra.apache.org > Subject: Re: opscenter doesn't work with cassandra 3.0 > > Unfortunately Datastax decided to discontinue Opscenter for open source > Cassandra, starting from version 2.2. > > Pitty > > On Wed, Jan 6, 2016 at 6:00 PM, Michael Shuler <mich...@pbandjelly.org > <mailto:mich...@pbandjelly.org>> wrote: > On 01/06/2016 10:55 AM, Michael Shuler wrote: > > On 01/06/2016 01:47 AM, Wills Feng wrote: > >> Looks like opscenter doesn't support cassandra 3.0? > > > > This is correct. OpsCenter does not support Cassandra >= 3.0. > > It took me a minute to find the correct document: > > http://docs.datastax.com/en/upgrade/doc/upgrade/opscenter/opscCompatibility.html > > <http://docs.datastax.com/en/upgrade/doc/upgrade/opscenter/opscCompatibility.html> > > According to this version table, OpsCenter does not officially support > Cassandra > 2.1. > > -- > Michael > > > > The information in this Internet Email is confidential and may be legally > privileged. It is intended solely for the addressee. Access to this Email by > anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be taken > in reliance on it, is prohibited and may be unlawful. When addressed to our > clients any opinions or advice contained in this Email are subject to the > terms and conditions expressed in any applicable governing The Home Depot > terms of business or client engagement letter. The Home Depot disclaims all > responsibility and liability for the accuracy and content of this attachment > and for any damages or losses arising from any inaccuracies, errors, viruses, > e.g., worms, trojan horses, etc., or other items of a destructive nature, > which may be contained in this attachment and shall not be liable for direct, > indirect, consequential or special damages in connection with this e-mail > message or its attachment.
