zipkin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordi Polo Carres <jcar...@mdsol.com>
Subject Re: Is it time to stop supporting Cassandra <3.11.3?
Date Mon, 06 May 2019 16:14:05 GMT
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 <adrian.f.cole@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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message