From dev-return-642-archive-asf-public=cust-asf.ponee.io@zipkin.apache.org Tue May 7 01:34:15 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1208418060F for ; Tue, 7 May 2019 03:34:14 +0200 (CEST) Received: (qmail 46265 invoked by uid 500); 7 May 2019 01:34:14 -0000 Mailing-List: contact dev-help@zipkin.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zipkin.apache.org Delivered-To: mailing list dev@zipkin.apache.org Received: (qmail 46248 invoked by uid 99); 7 May 2019 01:34:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2019 01:34:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6B098C2926 for ; Tue, 7 May 2019 01:34:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.246 X-Spam-Level: ** X-Spam-Status: No, score=2.246 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_TRY_3LD=1.647] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id uivaJ2xFbBmh for ; Tue, 7 May 2019 01:34:11 +0000 (UTC) Received: from mail-qk1-f196.google.com (mail-qk1-f196.google.com [209.85.222.196]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 80ADA5F117 for ; Tue, 7 May 2019 01:34:10 +0000 (UTC) Received: by mail-qk1-f196.google.com with SMTP id w25so131281qkj.11 for ; Mon, 06 May 2019 18:34:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:message-id:to:subject:in-reply-to:references :mime-version:content-transfer-encoding; bh=qNbhOSkkfgkDaYcMDlCKtaAa15XEc5jv0MYHRwKbEJA=; b=Bfp75q2vXRkTKltKpNZB2302g7XtgsoilUX6RhCIfVrC9sSjPRPmbVnzoLYfKUrZyP 3z0wLRapTBowksvVhWDEQVAD0Iu1mH+eL8WyfgeZWklZvgFzZ+JPvzzOXKnlsAaJAAVA 9zA1vvRAMPtwFYVyw0kyfdV9LOmzOQ0pN95zEHBAzUpyh48g5+C5EmWGt5PY+X4mBeLF 2UJf6+naM3fWdjwQq3mXgVBaZb8OYNmrDpdNzO4vlkncVaJzDl8zWoQB4o60YGMQ34GT KkDqOBuKQTngouHocuChJDFC+b2YMu7VMRqebqmy3fZQzw87HDa/BGZeo9ZSsiiOLRwf 1ZDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=qNbhOSkkfgkDaYcMDlCKtaAa15XEc5jv0MYHRwKbEJA=; b=cXS+i/t0PLUP0UXKTtaZGL4K9ZvhzH042J6v4QktPQEc2wtE8Eu1wYK6keP7Cui6ic /KIAjg8Ny28I7w2PtZzluOxN9o4mSM9EdsTDFqjKQIXZPA/bqZ1OhEmJ6HdXDCF1EW0e kHN5gfdpInV8RcDuA3nHDJ1xMryEpuoHzen30FrA1TNQ8EclidYNZ/3AgIdMz1N6Veq/ hCk7/aGUxu2xOAx5enGarUsBVaWiYFg4s15hE4GymExrtsEg5jWG8g3x+A28ym4zLEMK UlFfL+QRuY/6eotrCphWGk8WYC/ZU9ao+hIJM1OZsyPjo56njk8jaubQIWYbTUcg9gnz cUbw== X-Gm-Message-State: APjAAAUNDyGrC+wo73Hd1hu1IkJeuNM6VA/OoWk91UPcW+f1UYrVwGt6 enE85yAqoFc39aXiHcVrjfA= X-Google-Smtp-Source: APXvYqycPMOm/AWu9wJyWpKiDXWsrzhM4fqjOp3GmQDFUAh/ZO/8q7Dw1zj/MU9YScMiRJoGcct7Tg== X-Received: by 2002:a37:aa57:: with SMTP id t84mr6709531qke.169.1557192849308; Mon, 06 May 2019 18:34:09 -0700 (PDT) Received: from [192.168.0.104] ([166.62.251.169]) by smtp.gmail.com with ESMTPSA id 9sm6406100qkn.38.2019.05.06.18.34.08 (version=TLS1_1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 06 May 2019 18:34:08 -0700 (PDT) Date: Mon, 6 May 2019 21:33:55 -0400 From: Andriy Redko Reply-To: Andriy Redko Message-ID: <426893271.20190506213355@gmail.com> To: Adrian Cole , dev@zipkin.apache.org Subject: Re: Is it time to stop supporting Cassandra <3.11.3? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 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 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 >> >> 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