+1
—
AY
On 25 July 2018 at 08:49:15, Michael Shuler (mich...@pbandjelly.org) wrote:
I propose the following artifacts for release as 2.2.13.
sha1: 3482370df5672c9337a16a8a52baba53b70a4fe8
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative
+1
—
AY
On 25 July 2018 at 20:14:08, Jonathan Haddad (j...@jonhaddad.com) wrote:
+1
On Wed, Jul 25, 2018 at 11:35 AM Jeff Jirsa wrote:
> +1
>
> On Wed, Jul 25, 2018 at 12:16 AM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 3.11.3.
> >
> > s
+1
—
AY
On 25 July 2018 at 08:47:40, Michael Shuler (mich...@pbandjelly.org) wrote:
I propose the following artifacts for release as 3.0.17.
sha1: d52c7b8c595cc0d06fc3607bf16e3f595f016bb6
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.17-tentative
If this is about inclusion in 4.0, then I support it.
Technically this is *mostly* just a move+donation of some code from java-driver
to Cassandra. Given how important this seemingly is to the board and PMC for us
to not have the dependency on the driver, the sooner it’s gone, the better.
I’d b
ep 11, 2018 at 10:27 AM Aleksey Yeschenko
> wrote:
>
>> If this is about inclusion in 4.0, then I support it.
>>
>> Technically this is *mostly* just a move+donation of some code from
>> java-driver to Cassandra. Given how important this seemingly i
There are some nice benefits to GH PRs, one of them is that we could eventually
set up CircleCI hooks that would explicitly prevent commits that don’t pass the
tests.
But handling multiple branches would indeed be annoying. Would have to either
submit 1 PR per branch - which is both tedious and
I would like to propose CASSANDRA-15066 [1] - an important set of bug fixes
and stability improvements to internode messaging code that Benedict, I,
and others have been working on for the past couple of months.
First, some context. This work started off as a review of CASSANDRA-14503
(Internode
+1
> On 29 Jan 2021, at 14:30, Ekaterina Dimitrova wrote:
>
> +1(nb)
>
> On Fri, 29 Jan 2021 at 8:04, Mick Semb Wever wrote:
>
>>>
>>> The vote will be open for 72 hours (longer if needed). Everyone who has
>>> tested the build is invited to vote. Votes by PMC members are considered
>>> bind
CVE-2020-17516: Apache Cassandra doesn't enforce encryption setting on inbound
internode connections
Severity:
Important
Vendor:
The Apache Software Foundation
Versions Affected:
Cassandra 2.1.0 to 2.1.22
Cassandra 2.2.0 to 2.2.19
Cassandra 3.0.0 to 3.0.23
Cassandra 3.11.0 to 3.11.9
Descriptio
Correction: 3.11.x users should upgrade to 3.11.10. 3.11.24 doesn’t exist. Yet.
> On 1 Feb 2021, at 18:22, Aleksey Yeschenko wrote:
>
> CVE-2020-17516: Apache Cassandra doesn't enforce encryption setting on
> inbound internode connections
>
> Severity:
> Important
CASSANDRA-8285
<https://issues.apache.org/jira/browse/CASSANDRA-8285> Aleksey Yeschenko
Move
all hints related tasks to hints private executor Pierre's reproducer
represents something we weren't doing, but that users are. Is that now
being tested?
That particular issue will not ha
+1
--
AY
On April 27, 2015 at 17:47:17, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.5.
sha1: 3c0a337ebc90b0d99349d0aa152c92b5b3494d8c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.5-tentative
Artifa
How would it be different from creating an actual real extra table instead?
--
AY
On May 1, 2015 at 03:07:01, graham sanderson (gra...@vast.com) wrote:
Anyone here have an opinion; how realistic would it be to have a separate
memtable/sstable for static columns?
Begin forwarded message:
From
If the goal is to have branches that are always passing all the tests (aka
‘stable’ branches), then I don’t see any workarounds,
so +1 to this.
I’d go for branch names that are less likely to be confused w/ final
cassandra-X via autocomplete though: staging-2.0, staging-2.1, staging-trunk.
--
> Agreed as far as having staging branches vetoed by CI goes. Less sure about
> the edit-commit-in-place part as said above.
Right. That’s just an implementation detail (in place vs. extra fix up
commits). The latter is less annoying for the team in general, let’s do that
instead.
> If we do t
> The is still the problem of a commit coming into the staging dir after
> a previous commit that is being tested.
> When the first commit is merged to the stable branch it will include
> both tested and untested version.
How so? We’ll only be merging up to the latest tested ref into the stabl
Strictly speaking, the train schedule does demand that trunk, and all other
branches, must be releasable at all times, whether you like it or not (for the
record - I *don’t* like it, but here we are).
This, and other annoying things, is what be subscribed to tick-tock vs.
supported branches exp
that is not ours.
> >
> > On Thu, May 7, 2015 at 3:25 PM, Ariel Weisberg <
> > ariel.weisb...@datastax.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Whoah. Our process is our own. We don't have to subscribe to any
The switch will necessarily hurt 3.0 adoption, but I think we’ll live. To me,
the benefits (mostly access to lambdas and default methods, tbh) slightly
outweigh the downsides.
+0.1
--
AY
On May 7, 2015 at 19:22:53, Gary Dusbabek (gdusba...@gmail.com) wrote:
+1
On Thu, May 7, 2015 at 11:09
letely wired up (CHANGES.txt, commit
message, the works), so that it can be merged straight in. If it conflicts
significantly, it can be bumped back to the author/reviewer to refresh.
On Thu, May 7, 2015 at 4:16 PM, Aleksey Yeschenko
wrote:
> I would argue that we must *at least* do the
merged
branches before pushing either, in case of non-trunk patches?
+100 from me, but why the exception for trunk? Wouldn't it be easier to
wait for the dev branch tests to pass and then do all the merging at once
(2.0, 2.1,3.0, trunk)?
On Thu, May 7, 2015 at 1:21 PM, Aleksey Yeschen
Releasing a 2.2 now is indeed a good idea, +1 to that.
Regarding EOLs, however, there I don’t feel like dropping the planned 3.0.x
stabilisation branch is necessary.
I’d also say that having both 2.1.x and 2.2.x LTS branches is both 1) very
cheap for us and 2) is not really needed.
Here is why
That was an intentional decision on our side. Have a look at
https://issues.apache.org/jira/browse/CASSANDRA-5573 - Sylvain’s comment in
particular.
--
AY
On May 11, 2015 at 20:05:54, Brian O'Neill (b...@alumni.brown.edu) wrote:
Looks like the java-driver supplies the hack I need. (TokenRange
hly doubt that anybody using CQL2 is also someone who’d
already switch to 2.1.x or 2.2.x.
--
AY
On May 11, 2015 at 21:12:26, Jonathan Ellis (jbel...@gmail.com) wrote:
On Sun, May 10, 2015 at 2:42 PM, Aleksey Yeschenko
wrote:
> 3.0, however, will require a stabilisation period, just by
The drivers, actually, aren’t ready at all for 3.0 with 8099, because 6717 will
be pushed shortly after 8099, and break things.
--
AY
On May 11, 2015 at 23:29:13, Alex Popescu (al...@datastax.com) wrote:
On Sun, May 10, 2015 at 2:14 PM, Robert Stupp wrote:
> Instead of labeling it 2.2, I’d
Can you not alter the version of the drivers, though? 3.0 to 2.2?
--
AY
On May 11, 2015 at 23:38:00, Alex Popescu (al...@datastax.com) wrote:
On Mon, May 11, 2015 at 1:32 PM, Aleksey Yeschenko
wrote:
> The drivers, actually, aren’t ready at all for 3.0 with 8099, because 6717
> w
+1
--
AY
On May 13, 2015 at 19:00:45, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.0.15.
sha1: 418deaf6ca1d0ad2e95d13abc7b18dbd51e676e7
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.15-tentative
Artifa
+1
--
AY
On May 18, 2015 at 05:35:23, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.0-beta1.
sha1: 1735249ebfdbf139ca95507d591a324dfe81da33
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-beta1-tentativ
+1
--
AY
On June 5, 2015 at 18:07:11, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.6.
sha1: e469f32be180a1e493227111649d067a35201e97
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.6-tentative
Artifac
+1
--
AY
On June 5, 2015 at 18:28:28, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.0-rc1.
sha1: b0ae285bdc7377a64ed92f01c67ff46b40ecaac0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc1-tentative
+1
--
AY
On June 19, 2015 at 15:56:38, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.0.16.
sha1: 23e66a9d1c50e4331e8c1d212c2eeb940c5471fa
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.16-tentative
Arti
+1
--
AY
On June 19, 2015 at 16:01:04, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.7.
sha1: 718c144324d170535d4f1a1e79dd9869cce19ed1
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.7-tentative
Artifa
+1
--
AY
On July 6, 2015 at 20:05:47, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.8.
sha1: db39257c34152f6ccf8d53784cea580dbfe1edad
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative
Artifac
+1
--
AY
On July 7, 2015 at 01:10:30, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.0-rc2.
sha1: ebc50d783505854f04f183297ad3009b9095b07e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc2-tentative
I’m with Sylvain and Sam on this, as a person drinking from the JIRA firehose.
I’m fine with review happening on GH so long as it’s also mirrored on JIRA.
Someone could write a script that would automate this (take a PR, convert it to
a JIRA-formatted comment).
—
AY
On July 9, 2015 at 15:54:48
+1
--
AY
On July 17, 2015 at 21:08:06, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.0.
sha1: 437bb9de77f54aa5a4a6a634ab3d2c753a17b3fc
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-tentative
Artifa
+1
--
AY
On July 31, 2015 at 16:43:25, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0-alpha1.
sha1: b090ed6938c0fad792e51757384bd5ac7f35a301
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-alpha1-tenta
+1
--
AY
On August 22, 2015 at 06:15:28, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0-beta1.
sha1: 356c755a3b7aa1c71f72cf81fbe810670bd71de7
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-beta1-tenta
+1
--
AY
On August 25, 2015 at 17:01:36, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.9.
sha1: 7d74563a25cb34784ae3dca05fe503bdb60f5fe5
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.9-tentative
Arti
+1
--
AY
On August 25, 2015 at 20:45:38, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.1.
sha1: 323890647718d6e061349cf8cbe857b95bd02b13
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.1-tentative
Arti
+1
--
AY
On August 28, 2015 at 17:05:05, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.1.
sha1: 01a11fd2626d57bf0c8d0bce1e43060017592896
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.1-tentative
Arti
+1
--
AY
On September 5, 2015 at 01:58:05, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0-beta2.
sha1: 17528910b82391bd834f1fddce4ff7c9b34ad452
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-beta2-ten
+1
--
AY
On September 16, 2015 at 19:29:33, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.0.17.
sha1: 3aff44915edbd2bf07955d5b30fd47bf9c4698da
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.17-tentative
Changing +1 to -1, since we had to reopen CASSANDRA-10238.
--
AY
On September 17, 2015 at 17:43:52, Michael Shuler (mich...@pbandjelly.org)
wrote:
+1 non-binding
Commit that CR to cassandra-2.0 branch HEAD, leaving the tag where it is
and I can build DSC with it included :)
--
Michae
+1
--
AY
On September 18, 2015 at 15:48:18, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.0.17.
sha1: c4de752758c3cf7f5de5a92e4ede30e430a36255
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.17-tentative
+1
--
AY
On September 19, 2015 at 21:42:57, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0-rc1.
sha1: c95a7098cf77b5b8e96feb7c39aca8fec3a02f9c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-rc1-tentat
Compatible version of python-driver (3.0.0a3) and java-driver (3.0.0-alpha3)
will be published to pypi and maven later today.
In the meantime, you can use the versions bundled with Cassandra 3.0.0-rc1.
--
AY
On September 21, 2015 at 09:04:57, Jake Luciani (j...@apache.org) wrote:
The Cassandr
+1
--
AY
On October 1, 2015 at 07:18:10, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.10.
sha1: 78f2e7aa01d552454fd4270fee8d600c4433df5c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.10-tentative
Ar
+1
--
AY
On October 1, 2015 at 07:40:38, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.2.
sha1: ae9b7e05222b2a25eda5618cf9eb17103e4d6d8b
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.2-tentative
Arti
+1
--
AY
On October 12, 2015 at 19:06:08, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.11.
sha1: 4acc3a69d319b0e7e00cbd37b27e988ebfa4df4f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.11-tentative
A
+1
--
AY
On October 12, 2015 at 19:28:01, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.3.
sha1: 0c051a46c54fd1a2f151e1a68f4556faca02be8d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.3-tentative
Art
+1
--
AY
On October 13, 2015 at 19:59:01, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.3.
sha1: 89596682e8c495f0c6c76e0f7a21a6db96d00552
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.3-tentative
Art
+1
--
AY
On October 13, 2015 at 18:30:44, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.11.
sha1: a85afbc7a83709da8d96d92fc4154675794ca7fb
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.11-tentative
A
+1
--
AY
On 16 October 2015 at 21:34:06, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0-rc2.
sha1: 56a06d78f20237c15a2bc7fb79826818173baead
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-rc2-tentative
+1
--
AY
On 6 November 2015 at 21:35:06, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.0.
sha1: 96f407bce56b98cd824d18e32ee012dbb99a0286
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-tentative
Arti
With 3.0.0 vote to be over soon, tick-tock is officially starting, and we are
creating a new branch for cassandra-3.1 release.
New merge order: cassandra-2.2 -> cassandra-3.0 -> cassandra-3.1 -> trunk
- cassandra-3.0 branch is going to continue representing the 3.0.x series of
releases (3.0 bug
>
> > 2015-11-10 0:35 GMT+08:00 Aleksey Yeschenko :
> > >
> > > - cassandra-3.0 branch is going to continue representing the 3.0.x
> series
> > > of releases (3.0 bugfixes only, as no new feature are supposed to go
> into
> > &g
+1
--
AY
On 17 December 2015 at 19:42:33, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.2.
sha1: 9b655ac181e732e2c489e102d6742cad6f7029e6
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.2-tentative
Art
+1
--
AY
On 17 December 2015 at 19:41:25, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.1.1.
sha1: 8347d37716d318956591ab7d5688774a083e5bfb
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.1.1-tentative
Art
+1
--
AY
On 28 December 2015 at 14:27:26, Jonathan Ellis (jbel...@gmail.com) wrote:
Thrift has been officially frozen for almost two years and unofficially for
longer. [1] Meanwhile, maintaining Thrift support through changes like
8099 has been a substantial investment.
I propose depreca
+1
--
AY
On 8 January 2016 at 21:13:25, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.2.
sha1: 3c6dfa4aa0b9ffb0a48a02b949bff2a8406764e6
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.2-tentative
Artifacts
+1
--
AY
On 3 February 2016 at 16:51:35, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.5.
sha1: dd76858c7652541c7b137323f7b9e154686d6fba
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.5-tentative
Arti
+1
--
AY
On 3 February 2016 at 16:44:33, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.13.
sha1: d5b6d1b634f69709d2b3caa17cba52696ed2033d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.13-tentative
Ar
+1
--
AY
On 6 February 2016 at 06:11:33, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.3.
sha1: 5669c6967bbdd540f27aeebf5a2c258bc4defbe3
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.3-tentative
Artifact
+1
--
AY
On 8 February 2016 at 20:57:00, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.3.
sha1: b9bdd9ec648ad42d88b1377fe0e1e4ff3d162a91
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.3-tentative
Arti
Hello everyone,
I’ve compiled a short guide for contributors (who aren’t committers yet) about
how to properly contribute Cassandra patches:
https://docs.google.com/document/d/1d_AzYQo74de9utbbpyXxW2w-b0__sFhC7b24ibiJqjw/edit?usp=sharing
Following the outlined recommendations make the lives of
Once we have a new wiki, yup, definitely.
--
AY
On 9 February 2016 at 16:25:16, Michael Kjellman (mkjell...@internalcircle.com)
wrote:
Move to Wiki?
Sent from my iPhone
> On Feb 9, 2016, at 5:59 AM, Aleksey Yeschenko wrote:
>
> Hello everyone,
>
> I’ve compile
After repair is over, does the value settle? What CLs do you write to your
counters with? What CLs are you reading with?
--
AY
On 24 March 2016 at 06:17:27, Dikang Gu (dikan...@gmail.com) wrote:
Hello there,
We are experimenting Counters in Cassandra 2.2.5. Our setup is that we have
6 nod
comments about our setup?
During the repair, the counter value become inaccurate, we are still
playing with the repair, will keep you update with more experiments. But do
you have any theory around that?
Thanks a lot!
Dikang.
On Thu, Mar 24, 2016 at 11:02 AM, Aleksey Yeschenko
Hey.
Unlike 3.x series, there is no strict cycle for 2.1 and 2.2 updates. Generally
we go by the gut feeling (changes list is too long, or it’s been a while since
the last release).
That said, 2.2 list does indeed feel long now. If I were to guess, some time
this month (April) would be the dat
+1
--
AY
On 7 April 2016 at 23:11:17, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.5.
sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative
Artifac
+1
--
AY
On 11 April 2016 at 09:41:30, Benjamin Lerer (benjamin.le...@datastax.com)
wrote:
+1
On Sun, Apr 10, 2016 at 5:43 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 3.5.
>
> sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b
> Git:
>
> http://git-w
The answer will depend on how conservative you are.
The most conservative choice overall would be to go with the 2.2.x line.
3.0.x if you want to the new nice and shiny 3.0 things, but can tolerate some
risk (the branch has a lot of relatively new core code, and hasn’t yet been
tried out by as
+1
--
AY
On 22 April 2016 at 22:16:18, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.6.
sha1: 37f63ecc5d3b36fc115fd7ae98e4fc1f4bc2d1d6
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.6-tentative
Artifa
+1
--
AY
On 22 April 2016 at 22:13:19, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.14.
sha1: 209ebd380b641c4f065e9687186f546f8a50b242
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.14-tentative
Arti
Hello Weijian,
Please file a ticket with Cassandra JIRA - I’ll ping the person who implemented
hints compression and they’ll have a look.
--
AY
On 26 April 2016 at 10:44:00, weijian lin (linweiji...@gmail.com) wrote:
Hi,
When I enable hints_compression and set the compression class to
LZ
+1
--
AY
On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.6.
sha1: c17cbe1875a974a00822ffbfad716abde363c8da
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
Artifacts:
+1
--
AY
On 11 May 2016 at 02:55:11, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.6.
sha1: 52447873a361647a5e80c547adea9cf5ee85254a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
Artifact
Seconding the -1 (binding) for the same reasons.
--
AY
On 12 May 2016 at 23:44:46, Tyler Hobbs (ty...@datastax.com) wrote:
Based on CASSANDRA-11613 (and CASSANDRA-11760), I'm changing my vote to a
(non-binding) -1. There is a legit regression in upgrading non-frozen UDTs
that needs to be fi
+1
--
AY
On 1 June 2016 at 18:30:57, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.6.
sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
Artifacts:
As a member of that governing body (Cassandra PMC), I would much prefer not to
deal with the drivers as well.
And I’m just as certain that java-driver - and other driver communities - would
much rather prefer to keep their process and organisation instead of being
forced to conform to ours.
I’
...@carmanconsulting.com) wrote:
"Sr. Software Engineer at DataStax", imagine that.
On Sat, Jun 4, 2016 at 1:01 PM Aleksey Yeschenko wrote:
> As a member of that governing body (Cassandra PMC), I would much prefer
> not to deal with the drivers as well.
>
> And I’m just as ce
e intimate with the database, because it's the same
people developing it.
On Sat, Jun 4, 2016 at 1:06 PM Aleksey Yeschenko wrote:
> An eloquent and powerful response, but please, reply to my points instead
> of resorting to ad hominem arguments.
>
> In practical terms, wh
+1
--
AY
On 8 June 2016 at 14:21:58, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.7.
sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
Artifacts:
+1
--
AY
On 8 June 2016 at 16:31:35, Brandon Williams (dri...@gmail.com) wrote:
+1
On Wed, Jun 8, 2016 at 2:35 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 3.0.7.
>
> sha1: 040ac666ac5cdf9cd0a01a845f2ea0af3a81a08b
> Git:
>
> http://git-wip-us.apach
When in doubt, just open a JIRA. Thanks.
--
AY
On 15 June 2016 at 13:56:24, Anuj Wadehra (anujw_2...@yahoo.co.in.invalid)
wrote:
Should I raise JIRA ?? Or some develiper with knowledge of STCS could confirm
the bug ??
Anuj
Sent from Yahoo Mail on Android
On Tue, 14 Jun, 2016 at 12:
Schema will disagree during the upgrade itself, you can’t really work around
it. It will converge once you finish the upgrade, however.
--
AY
On 20 June 2016 at 04:21:02, Michael Fong (michael.f...@ruckuswireless.com)
wrote:
Hi,
We have recently encountered several schema disagreement issu
+1
--
AY
On 30 June 2016 at 20:31:11, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.1.15.
sha1: cb14186f8d6c2d1105a51e409c59a4e424958171
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.15-tentative
Artif
+1
--
AY
On 1 July 2016 at 15:59:02, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 2.2.7.
sha1: 092054170ec3daf92ec494a0db295037d3563229
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.7-tentative
Artifact
+1
--
AY
On 1 July 2016 at 16:41:00, Jake Luciani (j...@apache.org) wrote:
I propose the following artifacts for release as 3.0.8.
sha1: 8b21d9e9e975ea07023ae6ec4c04d997006c1a0a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.8-tentative
Artifact
I’d strike CASSANDRA-10383 off the list - there is no way it’s a blocker for
anything.
As for 9424, unless I die unexpectedly *and* nobody else picks up the work, it
should be fine for Nov.
Don’t see anything missing from the list.
--
AY
On 20 July 2016 at 15:59:34, Jason Brown (jasedbr...@g
+1 from me (and I don’t see any resistance to it either).
--
AY
On 18 July 2016 at 18:36:42, Jonathan Ellis (jbel...@gmail.com) wrote:
Except there really wasn't.
Patch submitter: "I want this in 2.1."
Reviewer: "Okay."
That's not exactly the bar we're looking for. To consider a perform
+1
--
AY
On 20 July 2016 at 22:48:09, Michael Shuler (mshu...@apache.org) wrote:
I propose the following artifacts for release as 3.8.
sha1: c3ded0551f538f7845602b27d53240cd8129265c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
Artifa
he patch against "a few hundred of thousands" without. I suppose
> one
> > could make a case that having repair over-stream by 3 order of magnitude
> in
> > some case is critical-ish. Note that I wouldn't oppose reverting this
> too,
> > as it doesn&#
I don’t think so, b/c https://issues.apache.org/jira/browse/CASSANDRA-12142
will allow us to develop them incrementally.
--
AY
On 20 July 2016 at 22:03:37, Jake Luciani (jak...@gmail.com) wrote:
Also, anything related to native protocol v5
https://issues.apache.org/jira/issues/?jql=labels%20%
3.10 most likely.
--
AY
On 21 July 2016 at 01:28:13, Jake Luciani (jak...@gmail.com) wrote:
Will that be in 3.x or 4?
I still think the issue is minor enough, and with 3.8 being extremely delayed,
and being a non-odd release, at that, we’d be better off just pushing it.
Also, I know we’ve been easy on -1s when voting on releases, but I want to
remind people in general that release votes can not be vetoed and on
o knowing that
2. has the small advantage of keeping the 3.0.x and 3.x versions released
more or less in lockstep).
>
> On Thu, Jul 21, 2016 at 8:19 AM, Aleksey Yeschenko
> wrote:
>
> > I still think the issue is minor enough, and with 3.8 being extremely
> &g
We don’t need to block 4.0 on #8110.
What we need is to block those sstable-format related tickets on *either* #8110
*or* 4.0.
#8110 itself can go anywhere in 3.x or 4.x.
--
AY
On 21 July 2016 at 15:38:58, Jason Brown (jasedbr...@gmail.com) wrote:
Sylvain,
In the large, yes, that is the b
uld recommend we go ahead and fix this before releasing, and to
> avoid a super compressed 3.9 window either retarget 3.8 for August, or 3.9
> for September.
>
> On Thu, Jul 21, 2016 at 9:58 AM, Aleksey Yeschenko
> wrote:
>
>> What we’d usually do is r
1 - 100 of 210 matches
Mail list logo
