You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zipkin.apache.org by Adrian Cole <ad...@gmail.com> on 2019/05/06 11:17:54 UTC
Is it time to stop supporting Cassandra <3.11.3?
Hi, team.
You may recall that we are maintaining double code for cassandra and
have been for years. This is due to the minimum requirement of our
"cassandra3" storage (3.11.3). Initially the gate was around those
using Datastax, but I am not sure if this problem is valid anymore or
not, as there aren't many details here:
https://docs.datastax.com/en/landing_page/doc/landing_page/compatibility.html
Regardless, we are hitting hard limitations of test runtimes, now.
Cassandra 4 is coming around the corner, which will imply a drop of
Cassandra 2.x support anyway. When should we drop support for
Cassandra <3.11.3?
Best,
-Adrian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Is it time to stop supporting Cassandra <3.11.3?
Posted by Andriy Redko <dr...@gmail.com>.
Hi Adrian,
My apologies if I am restating something you guys are aware of, but the
story of Cassandra 4.0 is an interesting one. It's been at least 2 years
since the rumours about Cassandra 4.0 release started to leak, but it is
not there yet (though 4.0 driver is out and it is **completely** different
beast).
The 2.x base is shrinking but I know a few organizations who a) stuck
with 2.x due to Thrift b) forked 2.x at some point and stayed with that
(applying own patches since than). I am not sure that these examples
are enough to keep the overhead of supporting 2.x for you guys, so
I would personally lean towards dropping it. Sadly, I am not sure
anyone is able to tell when Cassandra 4.0 is going to see the light
of the day, may be @Mick has some insights?
Best Regards,
Andriy Redko
AC> Here's the cassandra supported version table. While I've read blogs
AC> about Cassandra 4.0, I'm not sure if we can predict when that will be
AC> released. One complicating factor is that our "cassandra3" only works
AC> completely with Cassandra 3.11.3 and 3.11.4, due to indexing
AC> mechanics.
AC> So, if we follow Cassandra's policy we keep "cassandra" until 6 months
AC> after 4.0, as at least one of the below older versions are still
AC> supported until then.
AC> http://cassandra.apache.org/download/
AC> Apache Cassandra 3.0 is supported until 6 months after 4.0 release (date TBD).
AC> Apache Cassandra 2.2 is supported until 4.0 release (date TBD).
AC> Apache Cassandra 2.1 is supported until 4.0 release (date TBD) with
AC> critical fixes only.
AC> On Tue, May 7, 2019 at 12:14 AM Jordi Polo Carres <jc...@mdsol.com> wrote:
>> What's upstream policy wrt Cassandra <3.11.3 ?
>> I think we should just follow the same general principle. If maintained
>> upstream, we have to keep it (run CI etc), if not, it's best effort but not
>> ensured.
>> On Mon, May 6, 2019 at 4:18 AM Adrian Cole <ad...@gmail.com> wrote:
>> > Hi, team.
>> >
>> > You may recall that we are maintaining double code for cassandra and
>> > have been for years. This is due to the minimum requirement of our
>> > "cassandra3" storage (3.11.3). Initially the gate was around those
>> > using Datastax, but I am not sure if this problem is valid anymore or
>> > not, as there aren't many details here:
>> >
>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.datastax.com_en_landing-5Fpage_doc_landing-5Fpage_compatibility.html&d=DwIBaQ&c=fi2D4-9xMzmjyjREwHYlAw&r=Tbt5RfqX8JsodFyDrWf9DA8aXKZqHT-1uWccMDaGFlY&m=bGQQMgX-5l9O6PourKSgm16iizNMZFI0_X2NTkixh7k&s=jndCRev9g3jV3qP8hwFdcFnck7cFSrxzN8xJZD2_EJM&e=
>> >
>> > Regardless, we are hitting hard limitations of test runtimes, now.
>> > Cassandra 4 is coming around the corner, which will imply a drop of
>> > Cassandra 2.x support anyway. When should we drop support for
>> > Cassandra <3.11.3?
>> >
>> > Best,
>> > -Adrian
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> > For additional commands, e-mail: dev-help@zipkin.apache.org
>> >
>> >
>> --
>> *Jordi Polo Carres* | API bundle lead | Medidata Solutions Worldwide
>> <http://www.mdsol.com/>
>> Api bundle: api-bundle@mdsol.com
>> API standard: https://learn.mdsol.com/display/CA/MCC+API+Standard+V1
AC> ---------------------------------------------------------------------
AC> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
AC> For additional commands, e-mail: dev-help@zipkin.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Is it time to stop supporting Cassandra <3.11.3?
Posted by Adrian Cole <ad...@gmail.com>.
Here's the cassandra supported version table. While I've read blogs
about Cassandra 4.0, I'm not sure if we can predict when that will be
released. One complicating factor is that our "cassandra3" only works
completely with Cassandra 3.11.3 and 3.11.4, due to indexing
mechanics.
So, if we follow Cassandra's policy we keep "cassandra" until 6 months
after 4.0, as at least one of the below older versions are still
supported until then.
http://cassandra.apache.org/download/
Apache Cassandra 3.0 is supported until 6 months after 4.0 release (date TBD).
Apache Cassandra 2.2 is supported until 4.0 release (date TBD).
Apache Cassandra 2.1 is supported until 4.0 release (date TBD) with
critical fixes only.
On Tue, May 7, 2019 at 12:14 AM Jordi Polo Carres <jc...@mdsol.com> wrote:
>
> What's upstream policy wrt Cassandra <3.11.3 ?
> I think we should just follow the same general principle. If maintained
> upstream, we have to keep it (run CI etc), if not, it's best effort but not
> ensured.
>
> On Mon, May 6, 2019 at 4:18 AM Adrian Cole <ad...@gmail.com> wrote:
>
> > Hi, team.
> >
> > You may recall that we are maintaining double code for cassandra and
> > have been for years. This is due to the minimum requirement of our
> > "cassandra3" storage (3.11.3). Initially the gate was around those
> > using Datastax, but I am not sure if this problem is valid anymore or
> > not, as there aren't many details here:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.datastax.com_en_landing-5Fpage_doc_landing-5Fpage_compatibility.html&d=DwIBaQ&c=fi2D4-9xMzmjyjREwHYlAw&r=Tbt5RfqX8JsodFyDrWf9DA8aXKZqHT-1uWccMDaGFlY&m=bGQQMgX-5l9O6PourKSgm16iizNMZFI0_X2NTkixh7k&s=jndCRev9g3jV3qP8hwFdcFnck7cFSrxzN8xJZD2_EJM&e=
> >
> > Regardless, we are hitting hard limitations of test runtimes, now.
> > Cassandra 4 is coming around the corner, which will imply a drop of
> > Cassandra 2.x support anyway. When should we drop support for
> > Cassandra <3.11.3?
> >
> > Best,
> > -Adrian
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
>
> --
> *Jordi Polo Carres* | API bundle lead | Medidata Solutions Worldwide
> <http://www.mdsol.com/>
> Api bundle: api-bundle@mdsol.com
> API standard: https://learn.mdsol.com/display/CA/MCC+API+Standard+V1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Is it time to stop supporting Cassandra <3.11.3?
Posted by Jordi Polo Carres <jc...@mdsol.com>.
What's upstream policy wrt Cassandra <3.11.3 ?
I think we should just follow the same general principle. If maintained
upstream, we have to keep it (run CI etc), if not, it's best effort but not
ensured.
On Mon, May 6, 2019 at 4:18 AM Adrian Cole <ad...@gmail.com> wrote:
> Hi, team.
>
> You may recall that we are maintaining double code for cassandra and
> have been for years. This is due to the minimum requirement of our
> "cassandra3" storage (3.11.3). Initially the gate was around those
> using Datastax, but I am not sure if this problem is valid anymore or
> not, as there aren't many details here:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.datastax.com_en_landing-5Fpage_doc_landing-5Fpage_compatibility.html&d=DwIBaQ&c=fi2D4-9xMzmjyjREwHYlAw&r=Tbt5RfqX8JsodFyDrWf9DA8aXKZqHT-1uWccMDaGFlY&m=bGQQMgX-5l9O6PourKSgm16iizNMZFI0_X2NTkixh7k&s=jndCRev9g3jV3qP8hwFdcFnck7cFSrxzN8xJZD2_EJM&e=
>
> Regardless, we are hitting hard limitations of test runtimes, now.
> Cassandra 4 is coming around the corner, which will imply a drop of
> Cassandra 2.x support anyway. When should we drop support for
> Cassandra <3.11.3?
>
> Best,
> -Adrian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
--
*Jordi Polo Carres* | API bundle lead | Medidata Solutions Worldwide
<http://www.mdsol.com/>
Api bundle: api-bundle@mdsol.com
API standard: https://learn.mdsol.com/display/CA/MCC+API+Standard+V1