Re: Improve the performance of CAS

Hey all, Before we go bananas, let's see if Sylvain, the primary author of the original patch, has the opportunity to chime with some explanatory notes or other guidance. There may be some subtle points or considerations that are not obvious, and I'd hate to lose that context. Thanks, -Jason On

Re: 3.11.3

wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2. I'd propose we cut early next week (Monday) and anything that can get reviewed/committed from Kurt's list would be great. On Wed, Jun 6, 2018 at 5:22 AM, kurt greaves wrote: > We probably need to release 3.11.3 at some point soon

Re: 3.11 currently not building

Thanks for the quick turn around, Lerh and Paulo! On Thu, Jun 7, 2018 at 3:56 AM, Paulo Motta wrote: > Fixed bad merge to 3.11 with 7bb88deb4c6387fd67114543986774c903860de9. > Thanks for the heads up! > > 2018-06-07 2:34 GMT-03:00 Lerh Chuan Low : > > Hi guys, > > > > I saw your message on IRC J

reroll the builds?

Hey all, The recent builds were -1'd, but it appears the issues have been resolved (2.2.13 with CASSANDRA-14423, and 3.0.17 / 3.11.3 reverting CASSANDRA-14252). Can we go ahead and reroll now? Thanks, -Jason

Re: reroll the builds?

e are just flakes, but > if we only want to go on green builds perhaps we can either disable the > flakey tests or fix them up? If someone feels strongly we should fix > particular tests up please link a jira and I can take a whack at some of > them. > > -Joey > > On Tue, Ju

Re: reroll the builds?

to unblock those fixes. Will have an update shortly ... -Jason On Mon, Jul 23, 2018 at 9:18 AM, Jason Brown wrote: > Hi all, > > First, thanks Joey for running the tests. Your pass/fail counts are > basically what in line with what I've seen for the last several months. (I >

Re: reroll the builds?

lp out with the triage / rerunning dtests if needed. > Dinesh > > On Monday, July 23, 2018, 10:22:18 AM PDT, Jason Brown < > jasedbr...@gmail.com> wrote: > > I spoke with some people over here, and I'm going to spend a day doing a > quick triage of the failing dtest

Re: reroll the builds?

ey're the same / similar, we know at least we're at parity with the > previous release :) > Dinesh > > On Tuesday, July 24, 2018, 8:18:50 AM PDT, Jason Brown < > jasedbr...@gmail.com> wrote: > > TL;DR We are in a better place than we were for the 3.0.16 and

Re: [VOTE] Release Apache Cassandra 2.2.13

Ran the tests again, just for sanity sake, and all seems within acceptable levels. +1 On Wed, Jul 25, 2018 at 1:25 PM, Nate McCall wrote: > +1 > > On Wed, Jul 25, 2018, 7:49 PM Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.2.13. > > > > sha1: 3482370df5672c93

Re: [VOTE] Release Apache Cassandra 3.11.3 (Take 2)

Ran the tests again, just for sanity sake, and all seems within acceptable levels (in order to get the data loss bugs resolved). +1 On Wed, Jul 25, 2018 at 1:24 PM, Nate McCall wrote: > +1 > > On Wed, Jul 25, 2018, 7:46 PM Michael Shuler > wrote: > > > I propose the following artifacts for r

Re: [VOTE] Release Apache Cassandra 3.0.17 (Take 2)

Ran the tests again, just for sanity sake, and all seems within acceptable levels (in order to get the data loss bugs resolved). +1 On Wed, Jul 25, 2018 at 1:24 PM, Nate McCall wrote: > +1 > > On Wed, Jul 25, 2018, 7:47 PM Michael Shuler > wrote: > > > I propose the following artifacts for r

triage of recent dtest failures

Hi all, Now that the vote is on for the next releases, I've done an initial triage of the failed dtest runs from 2.2, 3.0, and 3.11 (based on my circleci runs). Below are the ten dtest failures I found most often (not exhaustive, but representative), and I opened up corresponding jiras for them.

Re: G1GC is now default

Hi Jon, Thanks for pointing that out. Looks like I missed that during the CASSANDRA-9608 review. Robert and I didn't discuss that online or offline, so it's something that snuck in. I don't have a personal preference for GC algs right now, but at a minimum it would probably be appropriate to retu

Re: G1GC is now default

restored CMS as the default GC alg in CASSANDRA-14636. Thanks, -Jason On Wed, Aug 8, 2018 at 4:33 PM, Jason Brown wrote: > Hi Jon, > > Thanks for pointing that out. Looks like I missed that during the > CASSANDRA-9608 review. Robert and I didn't discuss that online or o

upgrade guava on trunk before 9/1?

Hey all, Does anyone feel strongly about upgrading guava on trunk before the 9/1 feature freeze for 4.0? We are currently at 23.3 (thanks to CASSANDRA-13997), and the current is 26.0. I took a quick look, and there's about 17 compilation errors. They fall into two categories, both of which appear

Re: upgrade guava on trunk before 9/1?

, Ariel Weisberg wrote: > Hi, > > What do we get from Guava in exchange for upgrading? > > Ariel > > On Wed, Aug 15, 2018, at 10:19 AM, Jason Brown wrote: > > Hey all, > > > > Does anyone feel strongly about upgrading guava on trunk before the 9/1 > > feat

Re: Side Car New Repo vs not

+1 for separate repo. For pretty much all the same reasons Aleksey elucidated. On Tue, Aug 21, 2018 at 10:20 AM, Aleksey Yeshchenko wrote: > Sure, allow me to elaborate - at least a little bit. But before I do, just > let me note that this wasn’t a veto -1, just a shorthand for “I don’t like > t

Re: Supporting multiple JDKs

Some of our java8 code will not compile under java11 (see CASSANDRA-9608); the symbols have literally been removed (Unsafe.monitorEnter() / Unsafe.monitorExit() ). Setting -source to "8" will not help. Thus, we need two compilers for the foreseeable future. On Thu, Aug 23, 2018 at 3:44 PM, Suman

Re: [Discuss] Accept GoCQL driver donation

I find this idea interesting and worth a strong discussion. Something to consider is an argument floating around in the admin tool/side car discussion: if we take an existing project wholesale, we inherit all of it's design decision and technical debt (every project has these). On the other hand,

Re: NGCC 2018?

+1 to Jon's sentiment. Further, perhaps we should use that time after GA'ing 4.0 to poll our users what they need/want from the next major release of the database. On Wed, Sep 5, 2018 at 9:31 AM, Jonathan Haddad wrote: > I'm thinking a month or two after 4.0 would give us time to unwind after >

Re: UDF

Hi Robert, Thanks for taking on this work. Is this message a heads up that a patch is coming/complete, or to spawn a discussion about including this in 4.0? Thanks, -Jason On Tue, Sep 11, 2018 at 2:32 AM, Robert Stupp wrote: > In an effort to clean up our hygiene and limit the dependencies us

Re: Moving tickets out of 4.0 post freeze

Before we blanket update all of these, let's make sure they are not relevant for 4.0 - because some of them actually are. Some are docs, some are parent tickets, some are testing. Naively, here are some that are still 4.0: CASSANDRA-14746 CAS

Re: Testing 4.0 upgrading

Hi Tommy, Thank you for taking the time to start kicking the tires on the upgrade to 4.0. It looks like you've found two bugs: 1) "Unknown column coordinator_port during deserialization" (reported on 3.x nodes) - looks like the 4.0 node isn't filtering out a column from a system table that 3.0 d

Re: Revisit the proposal to use github PR

I'm with Sylvain and Aleksey. Our multi-branch strategy does not work well (if at all) with Github PR-style workflows (and, yes, I and most c* maintainers have played this game). The cassandra-dtests repo is different as we don't really branch there, so might be fine for Github PRs - except for the

Re: Revisit the proposal to use github PR

To clarify my position: Github PRs are great for *reviewing* code, and the commentary is much easier to follow imo. But for *merging* code, esp into our multi-branch strategy, PRs don't fit well, unless there's some technique I and perhaps others are unaware of. On Thu, Dec 13, 2018 at 9:47 AM Ari

Re: [VOTE] Change Jira Workflow

+1. On Mon, Dec 17, 2018 at 7:36 AM Michael Shuler wrote: > +1 > > -- > Michael > > On 12/17/18 9:19 AM, Benedict Elliott Smith wrote: > > I propose these changes < > https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals>* > to the Jira Workflow for the project. The vote

Re: Proposing an Apache Cassandra Management process

It looks like we have consensus to move forward with the sidecar I will be shepherding the project, and to that end, I'll create a repo against which we can start working. Thanks, -Jason On Fri, Nov 30, 2018 at 7:54 AM sankalp kohli wrote: > If no one has more feedback, we should create JIRAs

Sidecar repo created

Hello all, In moving the sidecar project forward, I've created a gitbox [1] repo for the cassandra-sidecar which is located at: git: https://gitbox.apache.org/repos/asf/cassandra-sidecar.git github: https://github.com/apache/cassandra-sidecar There are additional behaviors we can set on the repo

Re: Git Repo Migration

+1 for the migration. Thanks for owning and leading this, Sam On Fri, Jan 4, 2019 at 02:58 Sam Tunnicliffe wrote: > As per the announcement on 7th December 2018[1], ASF infra are planning to > shutdown the service behind git-wip-us.apache.org and migrate all > existing repos to gitbox.apache.or

Re: [VOTE] Release Apache Cassandra 2.2.0-rc1

+1 On Friday, June 5, 2015, Sylvain Lebresne wrote: > +1 > > On Fri, Jun 5, 2015 at 5:41 PM, Brandon Williams > wrote: > > > +1 > > > > On Fri, Jun 5, 2015 at 10:27 AM, Jake Luciani > wrote: > > > > > I propose the following artifacts for release as 2.2.0-rc1. > > > > > > sha1: b0ae285bdc7377a6

Re: [VOTE] Release Apache Cassandra 2.0.16

+1 On Fri, Jun 19, 2015 at 6:00 AM, Aleksey Yeschenko wrote: > +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.apach

Re: [VOTE] Release Apache Cassandra 2.2.0

+1 On Fri, Jul 17, 2015 at 4:02 PM, Aleksey Yeschenko wrote: > +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

Re: [VOTE] Release Apache Cassandra 3.0.0-alpha1

+1 On Fri, Jul 31, 2015 at 6:45 AM, Jonathan Ellis wrote: > +1 > > On Fri, Jul 31, 2015 at 8:42 AM, Jake Luciani wrote: > > > I propose the following artifacts for release as 3.0.0-alpha1. > > > > sha1: b090ed6938c0fad792e51757384bd5ac7f35a301 > > Git: > > > > > http://git-wip-us.apache.org/rep

Re: [VOTE] Release Apache Cassandra 3.0.0

+1 On Saturday, November 7, 2015, Josh McKenzie wrote: > +1 > > On Fri, Nov 6, 2015 at 4:34 PM, Jake Luciani > wrote: > > > I propose the following artifacts for release as 3.0.0. > > > > sha1: 96f407bce56b98cd824d18e32ee012dbb99a0286 > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=

Re: Proposal: deprecate Thrift now and remove support in 4.0

+1. It's finally time. On Mon, Dec 28, 2015 at 6:26 AM, Jonathan Ellis 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 deprecatin

Re: [VOTE] Release Apache Cassandra 3.2

+1 On Sunday, January 10, 2016, Sylvain Lebresne wrote: > +1 > > On Sat, Jan 9, 2016 at 12:32 PM, Robert Stupp > wrote: > > > +1 > > > > -- > > Robert Stupp > > @snazy > > > > > > > > -- > > Robert Stupp > > @snazy > > > Am 08.01.2016 um 22:12 schrieb Jake Luciani >: > > > > > > I propose the

Re: [VOTE] Release Apache Cassandra 3.2.1

+1 On Friday, January 15, 2016, Brandon Williams wrote: > +1 > > On Thu, Jan 14, 2016 at 9:03 PM, Jake Luciani > wrote: > > > I propose the following artifacts for release as 3.2.1. > > > > sha1: 2ac95bd6c5699a605e6f4256cb17b016c99e6dda > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?

Re: [VOTE] Release Apache Cassandra 2.1.13

+1 On Wed, Feb 3, 2016 at 5:44 AM, Jake Luciani 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 > Artifacts: > > https://

Re: [VOTE] Release Apache Cassandra 2.2.5

+1 On Wed, Feb 3, 2016 at 6:21 AM, Aleksey Yeschenko wrote: > +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.apach

Re: A short guid on how to contribute patches to Cassandra

Woo-hoo! Thanks :) On Tue, Feb 9, 2016 at 5:59 AM, Aleksey Yeschenko wrote: > 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__s

Re: [VOTE] Release Apache Cassandra 3.0.5

+1 On Thu, Apr 7, 2016 at 5:17 PM, Aleksey Yeschenko wrote: > +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.o

Re: Research on scalability bug finder for Cassandra

+1 to Tupshin's proposal: 10k nodes (massive clusters) really is the next frontier. I don't expect the vnodes to add that much to the gossip dissemination as the tokens per-node are sent out only a handful of times (when a node joins the ring, mostly). Without having hard data to back myself up, I

Re: Welcome new committers Carl Yeksigian and Stefania Alborghetti!

Woo-hoo! Congrats Carl and Stephania On Thursday, April 21, 2016, Jonathan Ellis wrote: > Belated congratulations to Carl (added as committer in January) and > Stefania (added this week)! > > Thanks for your hard work and we look forward to making Cassandra better > with you! > > -- > Jonathan E

Re: Cassandra Java Driver and DataStax

The client-server protocol is well defined in the Cassandra repo, so any one may implement a client library for any language. However, it is a far from trivial task, so not many folks build their own. Thus, already-built drivers tend to become the de facto standard, but we (the Apache Cassandra com

Re: [VOTE] Release Apache Cassandra 2.1.15

+1 On Friday, July 1, 2016, Sam Tunnicliffe wrote: > +1 > > On Fri, Jul 1, 2016 at 4:44 PM, Jonathan Ellis > wrote: > > > +1 on the release, but let's get those fixed for next time. > > > > On Thu, Jun 30, 2016 at 6:02 PM, Dave Brosius > > > wrote: > > > > > nits > > > > > > snappy-java and th

Re: Blockers for 4.0

CASSANDRA-8457 - nio MessagingService. Patch is up and awaiting review On Wed, Jul 20, 2016 at 7:40 AM, Jonathan Ellis wrote: > The plan of record has been to ship 4.0 in November, 12 months after 3.0. > But, there are a number of features that are going to cause backwards > incompatibility and

Re: Blockers for 4.0

ody 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...@gmail.com) wrote: > > CASSANDRA-8457 - nio MessagingService. Patch is up and awaiting review >

Re: Blockers for 4.0

Sylvain, In the large, yes, that is the best "have enough mechanism in place that no further ticket _have to_ wait for a major", but many of the tickets we are talking about makes changes to things we've all agreed can *only* happen at majors, as per the http://wiki.apache.org/cassandra/Compatibil

Re: Reminder: critical fixes only in 2.1

D'oh, too late to respond :) I was going to comment that leaving the non-critical commits in 2.1 is probably OK at this point (the deed has already been done), as long as we agree to become more rigorous in the future about critical bugs vs bugs vs minor enhancements vs major features and in which

Re: State of Unit tests (1 out of 100 passes in trunk)

>> Any reason not to draw a line in the sand for the next stabilization release (3.9)? +1 Josh, add me to the "test fixers" queue, as well. However, I think the authors of patches that break the build should also be on the hook for fixing problems, as well. On Wed, Jul 20, 2016 at 2:05 PM, Jo

Re: A proposal to move away from Jira-centric development

Chris, Can you give a few examples of other healthy Apache projects which you feel would be good example? Note: I'm not trying to bait the conversation, but am genuinely interested in what other successful projects do. Thanks Jason On Monday, August 15, 2016, Chris Mattmann wrote: > s/dev lis

Re: [ANN]: Cert management with self-signed CA for Cassandra (and presumably other Java stuff)

+1. I recently discovered that a coworker had built, more or less, the same thing just a month or two ago for internal/testing uses. And I know I've seen/heard it elsewhere, so yeah, this would be great! On Monday, August 22, 2016, Nate McCall wrote: > > > Any reason to not include this in the d

Re: Github pull requests

It seems to me we might get more contributions if we can lower the barrier to participation. (see Jeff Beck's statement above) +1 to Aleksey's sentiment about the Docs contributions. On Fri, Aug 26, 2016 at 9:48 AM, Mark Thomas wrote: > On 26/08/2016 17:11, Aleksey Yeschenko wrote: > > Mark, I,

Re: #cassandra-dev IRC logging

+1. How/where will this run? Is there any apache infra that we can make use of? On Fri, Aug 26, 2016 at 10:48 AM, Jake Luciani wrote: > +1 so long as it filters out the join/leave stuff :) > > On Fri, Aug 26, 2016 at 1:42 PM, Jeff Jirsa > wrote: > > > There exists a #cassandra-dev IRC channel t

Re: Github pull requests

D'oh, forgot to explicitly state that I am +1 one on the github PR proposal :) On Fri, Aug 26, 2016 at 11:07 AM, Jason Brown wrote: > It seems to me we might get more contributions if we can lower the barrier > to participation. (see Jeff Beck's statement above) > > +1

Re: #cassandra-dev IRC logging

derness.apache.org/manual.html> > [3] http://wilderness.apache.org/#meetings <http://wilderness.apache.org/ > #meetings> > [4] http://wilderness.apache.org/channels/#logs-#aurora < > http://wilderness.apache.org/channels/#logs-%23aurora> > > > On Aug 26, 2016, at

Re: #cassandra-dev IRC logging

of SCM changes in the cassandra project. > > On Fri, Aug 26, 2016 at 3:05 PM, Jeff Jirsa > wrote: > > > +1 to both as well > > > > On 8/26/16, 11:59 AM, "Tyler Hobbs" wrote: > > > > >+1 on doing this and using ASFBot in particular. > > >

Re: Github pull requests

ah > > > On Aug 26, 2016, at 1:38 PM, Andres de la Peña > wrote: > > > > +1 to GitHub PRs, I think it will make things easier. > > > > El viernes, 26 de agosto de 2016, Jason Brown > > escribió: > > > >> D'oh, forgot to explicitly sta

Gossip 2.0

Hi all, One of the problems I been thinking about for quite a while is how to improve the efficacy of cassandra's gossip, especially when dealing with large clusters (greater than 1,000 nodes). By reducing gossip overhead we can implement new features that require data to be disseminated cluster-w

Re: Support Multi-Tenant in Cassandra

The current implementation will probably be yanked when thrift as a whole is removed for 4.0. And I'm ok with that. That being said, there has been an undercurrent of interest over time about multitenancy, and I'm willing to entertain a renewed discussion. It might be instructive to see if any oth

Re: Support Multi-Tenant in Cassandra

of the project but there > might be some useful bits in there for anyone interested in MT. > > > On Sep 9, 2016, at 9:28 PM, Jason Brown > wrote: > > > > The current implementation will probably be yanked when thrift as a whole > > is removed for 4.0. And I'm ok

Re: [VOTE] Release Apache Cassandra 3.0.9

+1 On Thu, Sep 15, 2016 at 3:20 PM, Nate McCall wrote: > +1 > > On Fri, Sep 16, 2016 at 6:57 AM, Jake Luciani wrote: > > > I propose the following artifacts for release as 3.0.9. > > > > sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012 > > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassand

Re: [VOTE] Release Apache Cassandra 2.2.8

+1 On Friday, September 23, 2016, Brandon Williams wrote: > +1 > > On Fri, Sep 23, 2016 at 6:04 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.2.8. > > > > sha1: e9fe96f404b6a936ac5dbceb8f3934fe0d098a97 > > Git: > > http://git-wip-us.apache.org/repos/asf?p=

Re: [VOTE] Accept dtests Donation Into Project

+1 On Fri, Sep 30, 2016 at 11:53 AM, Brandon Williams wrote: > +1 > > On Fri, Sep 30, 2016 at 1:51 PM, Nate McCall wrote: > > > I propose we begin the process of accepting the contribution of the > > dtest codebase (https://github.com/riptano/cassandra-dtest) into the > > project. > > > > Backg

Re: [VOTE] Release Apache Cassandra 2.1.16

+1 On Thu, Oct 6, 2016 at 3:45 PM, Romain Hardouin wrote: > Hi, > I use the "current 2.1.16" (commit cdd535fcac4ba79bb371e8373c6504d9e3978853) > on > production in 5 DCs (82 nodes) out of 7 and it works well!I've just had to > add a MBean to track changes of the NTR queue length on top of cdd53

Re: [VOTE] Release Apache Cassandra 2.1.16

Ahh, sorry. I was +1'ing the proposed sha1 of 87034cd On Friday, October 7, 2016, Michael Shuler wrote: > On 10/07/2016 08:52 AM, Jason Brown wrote: > > +1 > > Jason, is this a vote for the proposed sha1: 87034cd release for 2.1.16, > or a comment to Romain? (gmail

Re: Rough roadmap for 4.0

Hey Nate, I'd like to add CASSANDRA-11559 (Enhance node representation) to the list, including the comment I made on the ticket (different storage ports for each node). For us, it's a great "would really like to have" as our group will probably need this in production within the next 1 year or les

Re: Moderation

Gary, I've just started looking into the moderator component due to this thread; I admit I did not know about it before (my fault). Yes, I would like to be added. Apparently, I need to file an INFRA ticket (as per https://www.apache.org/dev/committers.html#mailing-list-moderators), which I will do

Re: Moderation

you would like to be added. Did you > file the ticket - if so point me to it. If you haven't yet, no worries I > can still add you. Let me know. Thanks. > > On 2016-11-04 09:54 (-0700), Jason Brown wrote: > > Gary, > > > > I've just started looking into the mode

Re: Moderation

s/sis/is On Fri, Nov 4, 2016 at 10:12 AM, Jason Brown wrote: > Chris, > > Yes, I would like to be added, and here sis the ticket I filed: > https://issues.apache.org/jira/browse/INFRA-12858. > > Thanks, > > -Jason > > On Fri, Nov 4, 2016 at 10:10 AM, Chris Mattman

Re: Rough roadmap for 4.0

> I have other follow up issues like getting seeds from Amazon API, or from > > JNDI/ DNS, etc. > > > > I was hoping 12627 was an easy way to grease the wheels. > > > > > > On Fri, Nov 4, 2016 at 8:39 AM, Jason Brown > wrote: > > > > > Hey Nat

Re: [VOTE] Close client-...@cassandra.apache.org mailing list

+1 On Sunday, November 6, 2016, Gary Dusbabek wrote: > +1 let's close it. > > Gary. > > > On Mon, Nov 7, 2016 at 5:11 AM, Jeff Jirsa > wrote: > > > There exists a nearly unused mailing list, > client-...@cassandra.apache.org > > [0]. > > > > This is a summary of the email threads over the past

Re: New 'cassandra-builds' git repo, or in-tree?

+1, even though I think you've already done it ;) Thanks! On Fri, Nov 11, 2016 at 1:51 PM, Michael Shuler wrote: > On 11/11/2016 01:02 PM, Nate McCall wrote: > >> It may also allow a > >> lower barrier for contributors interested in helping with specifically > >> build/test infrastructure. > > >

Re: Rough roadmap for 4.0

Jason, That's a separate topic, but we will have a different vote on how the branching/release strategy should be for the future. On Thursday, November 17, 2016, jason zhao yang wrote: > Hi, > > Will we still use tick-tock release for 4.x and 4.0.x ? > > Stefan Podkowinski >于2016年11月16日周三 > 下午4

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Hey all, Here's an update on the following items: NIO meassing/streaming - first is being reviewed; second is getting close to review time Gossip 2.0 - TL;DR I don't plan on moving cluster metadata (the current "gossip" data) onto the new gossip/membership stack until 5.0, so it's not a 4.0 block

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

; > wrote: > >>>>> > >>>>>>> While stability is important if we push back large "core" changes > >>>>> until later we're just setting ourselves up to face the same issues > >> later on > >>>

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

hem. > > Otherwise we will forever be basing versions on the poor test saps who > decide they are willing to risk all to upgrade to the cutting edge, and > why, everyone believes in the adage, don't upgrade until at least .6 > > --dave > > > On 11/20/2016 09:50 AM, Jas

Re: [VOTE] 3.X branch feature freeze

+1 On Fri, Jan 13, 2017 at 10:16 AM, Benjamin Roth wrote: > Progress: > Yes and no. I made a patch that made our cluster stable performance wise > but introduces a consistency issue I am aware of. We can deal with it and I > prefer this over severe performance problems. But this is nothing you c

Re: Wrapping up tick-tock

It's fine to limit the minimum time between major releases to six months, but I do not think we should force a major just because n months have passed. I think we should up the major only when we have significant (possibly breaking) changes/features. It would seem odd to have a 6.0 that's basically

Re: Instaclustr Masters scholarship

Ben, This is pretty cool! Almost wish I could apply ;) >> "Distributed database systems are relatively new technology" https://www.ietf.org/rfc/rfc677.txt.pdf - lol, 1975 :) -Jason On Tue, Feb 7, 2017 at 7:26 PM, Ben Bromhead wrote: > As part of our commitment to contributing back to the Apac

New committers announcement

e keep the excellent contributions coming. Thanks, -Jason Brown

Re: New committers announcement

.. and I misspelled Stefan's last name :(. It should read "Stefan Podkowinski". All apologies, Stefan. On Tue, Feb 14, 2017 at 1:31 PM, Jason Brown wrote: > Hello all, > > It's raining new committers here in Apache Cassandra! I'd like to > announce the fol

Re: [VOTE] Release Apache Cassandra 2.1.17

+1 On Wed, Feb 15, 2017 at 5:16 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.17. > > sha1: 943db2488c8b62e1fbe03b132102f0e579c9ae17 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.17-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.2.9

+1 On Wed, Feb 15, 2017 at 5:16 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.9. > > sha1: 70a08f1c35091a36f7d9cc4816259210c2185267 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.9-tentative > Artifacts: > https://

Re: [VOTE] Release Apache Cassandra 3.0.11

+1 On Wed, Feb 15, 2017 at 5:15 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.11. > > sha1: 338226e042a22242645ab54a372c7c1459e78a01 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.11-tentative > Artifacts: > https:

Re: Upgrade the jna version to 4.3.0

Hi Amit, Can you open a Jira for that? Also we can figure out which branches to target for the upgrade on the Jira. Thanks, Jason On Sun, Mar 5, 2017 at 08:25 Amitkumar Ghatwal wrote: > > > Hi All, > > Could you please upgrade the jna version present in the github cassandra > location : > http

Re: [VOTE] Release Apache Cassandra 3.0.12

+1 On Wed, Mar 8, 2017 at 5:38 AM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 7 March 2017 at 16:15:32, Michael Shuler (mich...@pbandjelly.org) > wrote: > > I propose the following artifacts for release as 3.0.12. > > This release addresses a possible 2.1->3.0 upgrade issue[3], along with

Testing and jira tickets

Hey all, A nice convention we've stumbled into wrt to patches submitted via Jira is to post the results of unit test and dtest runs to the ticket (to show the patch doesn't break things). Many contributors have used the DataStax-provided cassci system, but that's not the best long term solution. T

Re: Testing and jira tickets

or a regression as a result of the > > change, even though I've asked twice for that information. > > > > In addition to "does this thing break anything" we should be asking "how > > does this patch affect performance?" (and were the appropriate do

Re: Testing and jira tickets

t be a big problem because if someone is > doing a lot of reviews they should be a committer right? > > Regards, > Ariel > > On Thu, Mar 9, 2017, at 01:51 PM, Jason Brown wrote: > > Hey all, > > > > A nice convention we've stumbled into wrt to patches sub

jira ticket assignment

Hey all, Currently, when a new contributor wants to have a ticket assigned to themselves, they cannot due to JIRA permissions. The contributor (or someone on behalf of the contributor) usually needs to contact the dev-channel and ask for the magical permissions to be granted, and there's only a ha

Re: Code quality, principles and rules

>> do we have plan to integrate with a dependency injection framework? No, we (the maintainers) have been pretty much against more frameworks due to performance reasons, overhead, and dependency management problems. On Thu, Mar 16, 2017 at 2:04 PM, Qingcun Zhou wrote: > Since we're here, do we

Re: Code quality, principles and rules

As someone who spent a lot of time looking at the singletons topic in the past, Blake brings a great perspective here. Figuring out and communicating how best to test with the system we have (and of course incrementally making that system easier to work with/test) seems like an achievable goal. On

Re: Code quality, principles and rules

h small patches, that might be harder to achieve - however, as the patch should come with *some* tests (unless it's a truly trivial patch), it might just work itself out. On Fri, Mar 17, 2017 at 11:19 AM, Jason Brown wrote: > As someone who spent a lot of time looking at the singletons top

Re: [VOTE] Ask Infra to move github notification emails to commits@

+1 On Mon, Mar 20, 2017 at 3:02 PM, Brandon Williams wrote: > +1, we've had to explain this a thousand times here. > > On Mon, Mar 20, 2017 at 5:00 PM, Jeff Jirsa wrote: > > > There's no reason for the dev list to get spammed everytime there's a > > github PR. We know most of the time we prefer

Re: [VOTE] Ask Infra to move github notification emails to pr@

+1 On Mon, Mar 20, 2017 at 18:21 Anthony Grasso wrote: > +1 > > On 21 March 2017 at 09:32, Jeff Jirsa wrote: > > > There's no reason for the dev list to get spammed everytime there's a > > github PR. We know most of the time we prefer JIRAs for real code PRs, > but > > with docs being in tree an

Re: [DISCUSS] Implementing code quality principles, and rules (was: Code quality, principles and rules)

re: code coverage (this could become it's own thread, and probably should) As somebody working on a new large feature (CASSANDRA-8457), I have a few thoughts/observations about code coverage. As a preface, though, I'll point out that we have jacoco (http://www.jacoco.org/jacoco/trunk/index.html) a

[VOTE] self-assignment of jira tickets

Hey all, Following up on my emai

Re: [VOTE] self-assignment of jira tickets

oops, hit sent too early. will send another email shortly On Wed, Mar 29, 2017 at 6:14 AM, Jason Brown wrote: > Hey all, > > Following up on my emai >

[VOTE] self-assignment of jira tickets

thout needing to be added to the contributors group first. https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to get this done with INFRA. Vote will be open for 72 hours. Thanks, -Jason Brown

  1   2   3   >