Re: OOM when running hector's unit tests at 0.7.0

An additional point - we just added the system_* methods and this test class does an add, rename then drop for both CF and keyspace. On 9/18/10, Ran Tavory ran...@gmail.com wrote: I started seeing OOM when running hector's unit-tests on 0.7.0. The OOM is in cassandra's code so either there had

Re: MessagePack

There is an open issue awaiting additional info from the submitter: https://issues.apache.org/jira/browse/CASSANDRA-1735 On Tue, Nov 16, 2010 at 1:10 PM, bbo...@gmail.com wrote: a friend made me aware of MessagePack today:   http://msgpack.org/ do any of you have any experience with

Re: Question about ByteBuffer positions

for your own code, I would stay with duplicate(), slice() and similar and just assume we will do something fancier than we currently are one day. The overhead of those methods is really small as it's just pointers to the same underlying buffer. On Tue, Nov 23, 2010 at 5:42 PM, Ed Anuff

Re: Reducing confusion around client libraries

On Fri, Dec 3, 2010 at 11:59 AM, Paul Brown paulrbr...@gmail.com wrote: One way that this could be accomplished with a relatively even hand is to ensure that the relative liveliness of the client libraries is apparent on the page, e.g., a most recent release date, the target language (and

Re: Avro RPC?

We encapsulated the transport in Hector a while ago, stubbing out the avro stuff when we did. Fwiw, we have yet to receive a single request for building it out. Implementing a different approach like CQL is far more compelling to me than maintaining two transports that are more or less feature

Re: Dependencies need to run the hectors examples

A decent list is available here: https://github.com/rantav/hector/wiki/Current-Dependencies This is most easily accomplished by using a build system such as Maven or Ant to manage project dependencies. Please direct any Hector-specific questions to hector-us...@googlegroups.com in the future.

Re: Prepared Statement support (CASSANDRA-2475)

Hi Eric, Thanks for the follow up. I see the point of increased complexity on the clients keep coming up in the references, but the truth is that we've pretty much all had to abstract serialization to some degree or another just to keep up with changes. At least in the case of Hector, dealing

Re: Proposal: freeze Thrift starting with 2.1.0

. +1 (non-binding). -- - Nate McCall Austin, TX @zznate Co-Founder Sr. Technical Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

e the same question for *Map* type. > > Thanks for your help. > > === > Best Regards > -- - Nate McCall Austin, TX @zznate CTO Apache Cassandra Consulting http://www.thelastpickle.com

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 10:05 AM, James Carman wrote: > So why not just donate the Java driver and keep that in house? Cassandra is > a Java project. Makes sense to me. > > I won't deny there is an argument to be made here, but as a former client maintainer (Hector),

Re: Cassandra Java Driver and DataStax

com> wrote: > Who said the driver has to be released with the database? > > On Sat, Jun 4, 2016 at 12:29 PM Nate McCall <n...@thelastpickle.com> > wrote: > > > On Sat, Jun 4, 2016 at 10:05 AM, James Carman < > ja...@carmanconsulting.com> > > wrote:

Re: Cassandra Java Driver and DataStax

m suggesting is that the driver project be somewhat of a subproject > or a "module". It can still have its own life cycle, just like it does now. > > On Sat, Jun 4, 2016 at 12:44 PM Nate McCall <n...@thelastpickle.com> > wrote: > > > It doesnt. But then we add complexity in

Re: Cassandra Java Driver and DataStax

ing body (the PMC)? > > What I am suggesting is that the driver project be somewhat of a > subproject > > or a "module". It can still have its own life cycle, just like it does > now. > > > > On Sat, Jun 4, 2016 at 12:44 PM Nate McCall <n...@thelastpickle.co

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 12:07 PM, James Carman <ja...@carmanconsulting.com> wrote: > > On Sat, Jun 4, 2016 at 1:05 PM Nate McCall <n...@thelastpickle.com> wrote: > > > Whereas the health of my company and title rely heavily on a thriving open > > source community, y

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

+1 (non-binding) Thanks Jeremiah. This is moving us in the right direction. On Wed, Aug 17, 2016 at 5:31 AM, Jeremiah D Jordan < jeremiah.jor...@gmail.com> wrote: > Back to the topic at hand. First, let us establish that all of this stuff > will be happening “on the mailing lists”, all JIRA

Re: Cassandra on Google Summer of Code 2017

Sorry for the top post, but just want to make sure everyone has the details: If any committers want to be involved in this, the ASF is filling this out as a whole so we don't need to do too much on a project level. ASF details for mentorship (including GSoC) can be found here:

Re: [VOTE] Release Apache Cassandra 3.10 (Take 5)

> I propose the following artifacts for release as 3.10. > > sha1: 3cf415279c171fe20802ad90f181eed7da04c58d +1

Re: [VOTE] Release Apache Cassandra 3.10 (Take 4)

What was the resolution on this? Looks like we resolved/Fixed CASSANDRA-13058. Can we re-roll and go again? On Tue, Jan 17, 2017 at 4:26 AM, Sylvain Lebresne wrote: > I'm a bit sorry about it, but I'm kind of -1 on the account of >

Re: tracing improvements

I think all three of these have merit. Per-CF tracing would be the most immediately useful (and likely least impactful). For #3, I like the interface approach over exposing internal APIs. You can sort of kind of do this with custom QueryProcessor, but having something specific to tracing would be

Re: tracing improvements

I do miss this from other RDBMSs. If you could come up with a light-touch way to do this, I think a lot of people would be quite happy about it. On Wed, Jan 25, 2017 at 2:02 PM, Corentin Chary wrote: > On Wed, Jan 25, 2017 at 9:55 PM, Sam Overton

Re: Perf regression between 2.2.5 and 3.11

There was CASSANDRA-12269 fixed in 3.10 recently as well. On Wed, Jan 25, 2017 at 11:47 AM, Dikang Gu wrote: > We still see perf regression with the otc_coalescing_strategy disabled, and > on 3.0.10 branches as well. We can share our stress test results here. > > @Sankalp,

Re: [VOTE] Release Apache Cassandra 2.1.17

+1

Re: [VOTE] Release Apache Cassandra 3.0.11

+1

Re: [VOTE] Release Apache Cassandra 2.2.9

+1

Re: [VOTE] Release Apache Cassandra 3.10 (Take 4)

Indeed I conflated the two - thanks Sylvain. On Mon, Jan 23, 2017 at 11:19 PM, Sylvain Lebresne <sylv...@datastax.com> wrote: > On Mon, Jan 23, 2017 at 2:31 AM, Nate McCall <zznat...@gmail.com> wrote: > >> What was the resolution on this? >> >> Looks like we re

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

> Major new features and architectural improvements should be > discussed first here, then when consensus on design is achieved, moved to > Jira for implementation and review. > So the goal is to mitigate some of the (in most cases necessary) noise that bloated CASSANDRA-8844? (There are others,

Re: Where would a Cassandra equivalent of mysqldumpslow be placed?

Placing it in tools/bin should be a good place to start. Thanks! On Mon, Feb 27, 2017 at 6:01 PM, Murukesh Mohanan wrote: > For CASSANDRA-13000 (slow query log analysis tool), I uploaded a script. If I > were to submit it as a patch, where should I place it? In bin/,

Re: [VOTE] Release Apache Cassandra 3.0.9

as well as the debian package are also available here: > http://people.apache.org/~jake > > The vote will be open for 72 hours (longer if needed). > > [1]: https://goo.gl/JKkE05 (CHANGES.txt) > [2]: https://goo.gl/Hi8X71 (NEWS.txt) > -- - Nat

Re: Can we change the number of vnodes on existing nodes?

gt; > There seems no way to change the number of vnodes on existing nodes, is > there any reason that we can not support it? It should not be too different > from moving the node with one single token, right? > > Thanks > Dikang > -- - Nate McCall Welli

Re: [VOTE] Release Apache Cassandra 2.2.8

+1 On Sat, Sep 24, 2016 at 11:04 AM, 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=cassandra.git;a=shortlog;h=refs/tags/2.2.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

+1 On Tue, Sep 27, 2016 at 3:52 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.9

+1 On Tue, Sep 27, 2016 at 4:12 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.9. > > sha1: c1fa21458777b51a9b21795330ed6f298103b436 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.9-tentative >

Re: A home for 4.0

Thanks Sylvain - since we have a few new folks, can you poke the docs on committing to include a bit about the merge order? On Fri, Sep 30, 2016 at 2:56 AM, Michael Shuler wrote: > Thanks! To clarify, yes, I was just being silly. We mostly use the > base.version in

Re: [VOTE] Release Apache Cassandra 2.1.16

+1 On Thu, Oct 6, 2016 at 12:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative

[Discuss] Adding dtest to project

[Moved from PMC as there is nothing really private involved] DataStax has graciously offered to contribute cassandra-dtest [0] to the project. There were, however, two issues noted by Jonathan when he presented the offer to the PMC: 1. dtest mixes tests for many cassandra versions together in a

Re: Guidelines for test coverage

tion tests with every patch. > Thoughts on this? > > Thanks, > Sankalp > -- - Nate McCall Wellington, NZ @zznate CTO Apache Cassandra Consulting http://www.thelastpickle.com

Re: #cassandra-dev IRC logging

gt; > >On Fri, Aug 26, 2016 at 1:40 PM, Jason Brown < > jasedbr...@gmail.com> > > > > > wrote: > > > > > > > > > > > >> @Dave ASFBot looks like a winner. If others are on board with > > this, > > > I > > > > > can > > > > > >> work on getting it up and going. > > > > > >> > > > > > >> On Fri, Aug 26, 2016 at 11:27 AM, Dave Lester < > > > dave_les...@apple.com> > > > > > >> wrote: > > > > > >> > > > > > >> > +1. Check out ASFBot for logging IRC, along with other > > > > > integrations.[1] > > > > > >> > > > > > > > > > > > > > > > > > > > > > -- - Nate McCall Wellington, NZ @zznate CTO Apache Cassandra Consulting http://www.thelastpickle.com

Re: Github pull requests

b > > > > the official repo, with an Apache mirror, rather than the other way > > > > around. (Maybe this is required to accept pull requests, I am not > > sure.) > > > > > > > > Should we revisit our policy here? > > > > > > >

Re: Github pull requests

> > > Nate, since you have experience with this from Usergrid, can you figure out > what we need to do to make this happen and follow up with infra? > Yep - i'll look into this.

Re: Github pull requests

ps://cwiki.apache.org/confluence/display/JCLOUDS/Git+workflow Maybe we just amend our 'how-to-commit' with similar details as the two references above? http://cassandra.apache.org/doc/latest/development/how_to_commit.html -Nate On Mon, Aug 29, 2016 at 10:44 AM, Nate McCall <n...@thelastpickle.com&g

Get in on the fun!

Folks, We've made some good efforts growing the committer pool recently and it would be super cool to start getting more people involved in day to day reviews and commits. You can find a guide of how to do this here: http://cassandra.apache.org/doc/latest/development/how_to_commit.html Honestly,

Re: [VOTE] Accept dtests Donation Into Project

Yaskevich <pove...@gmail.com> wrote: > +1 > > On Mon, Oct 3, 2016 at 7:54 AM, Aleksey Yeschenko <alek...@apache.org> > wrote: > >> +1 >> >> -- >> AY >> >> On 30 September 2016 at 19:51:32, Nate McCall (zzn...@apache.org) wrote: >>

[VOTE] Accept dtests Donation Into Project

I propose we begin the process of accepting the contribution of the dtest codebase (https://github.com/riptano/cassandra-dtest) into the project. Background discussion thread here:

Re: [VOTE] Release Apache Cassandra 2.1.16

Hi Romain, I appreciate you speaking up about this, but I stuck with my +1 in order to get 2.1.16 with the NTR fix out since I have seen CASSANDRA-11363 with every recent client installation. Also, running the patch in production produced results satisfactory enough to me to preclude the need for

Re: [VOTE] Release Apache Cassandra 2.1.16

> It's too minor for a re-roll, and safe enough to just apply yourself if you > want it. Agreed. > > On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler <mich...@pbandjelly.org> > wrote: > >> Nate, do think CASSANDRA-12758 should go to 2.1.x? >> >> -- >

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

+1 On Mon, Nov 7, 2016 at 6:11 PM, 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 12 months on that list: > > 1) ApacheCon Seville CFP Close notice > 2) Datastax

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

+1 On Wed, Nov 9, 2016 at 9:08 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative >

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

+1 On Wed, Nov 9, 2016 at 9:09 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative >

Re: Message from the ASF Board or Directors about recent Cassandra discussions

Bertrand, Thank you very much for reaching out. I put the following in the upcoming board report, but I'll repeat it here because I think it sums things up: "If nothing else, it's clear we all care very deeply about having successful open source software projects." To that end, let's all move

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

Ben, Thank you for providing two thoughtful, concrete recommendations. There is some good feedback in general on this thread, but I'm calling Ben's response out because point #1 is important to discuss and point #2 is immediately actionable. > 1) I think some process of assigning a committer of a

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

Good catch. Thanks everyone for speaking up about these. Changing mine to -1 On Nov 10, 2016 2:44 AM, "Sam Tunnicliffe" wrote: > > -1 from me too due to #12877. I also agree with Alex's suggestion of > reverting #11990 and re-rolling. > > On Wed, Nov 9, 2016 at 1:20 PM,

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

I like the idea of a goal-based approach. I think that would make coming to a consensus a bit easier particularly if a larger number of people are involved. On Tue, Nov 8, 2016 at 8:04 PM, Dikang Gu wrote: > My 2 cents. I'm wondering is it a good idea to have some high level

Re: Rough roadmap for 4.0

ar > goals or a certain theme for the release should make it easier to decide > what to review and where to decline. Does that make sense? > > On Fri, Nov 4, 2016 at 3:47 AM, Nate McCall <zznat...@gmail.com> wrote: > >> It was brought up recently at the PMC level that

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

. On Sat, Nov 5, 2016 at 10:38 AM, Nate McCall <zznat...@gmail.com> wrote: > [Moved to a new thread because this topic is important by itself] > > There are some excellent points here - thanks for bringing this up. > >> What can inspiring developers contribute to 4.0 >&g

Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

[Moved to a new thread because this topic is important by itself] There are some excellent points here - thanks for bringing this up. > What can inspiring developers contribute to 4.0 > that would move the project forward to it’s goals and would be very likely > included in the final release?

Re: Batch read requests to one physical host?

I see a few slightly different things here (equally valuable) in conjunction with CASSANDRA-10414: - Wanting a small number of specific, non-sequential rows out of the same partition (this is common, IME) and grouping those - Extending batch semantics to reads with the same understanding with

Re: Low hanging fruit crew

That's a good idea, Ed, thanks for bringing this up. Kurt, if you are offering up resources for review and test coverage, there is work out there. Most immediately in the department of reviews for "Patch Available." While not quite low-hanging fruit, it's helpful to have non-committers look

Re: Low hanging fruit crew

Thanks Jeremy. To come back to the original idea, for an LHF crew how about as these: - a weekly(?) list of LHF tickets sent to dev list - sharing fliters of the above (can we put these on the how to contribute page?) - adopt Jeff B.'s idea of tagging LHF your own self as part of our

Re: Re[3]: Histogram error "Unable to compute ceiling for max when histogram overflowed"

Open a new issue and link to CASSANDRA-11063. Including a test case addressing your issue that fails after the 11063 change would be ideal as well. Either way, thanks for the continued attention on this. On Fri, Oct 21, 2016 at 4:06 AM, Владимир Бухтояров wrote: > I

Re: Proposal - 3.5.1

> I’m not sure it makes sense to have separate features/stability releases in > that world. 4.0.x will be stable, every 4.x will be a dev release on the road > to 5.0. > +1. Much easier to understand and it's 'backwards compatible' (sort of) with wherever we leave 3.x. Still keeping 4.x on

Re: Use of posix_fadvise

Benedict mentioned it briefly above, but the earliest / most detailed conversation on this can be found in CASSANDRA-1470. You may also find some stuff from the dev list and other issues around the same time from specifically from Chris G. and Peter S. (names on that ticket) as, IIRC, they were

Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 3)

+1 On Sat, Nov 12, 2016 at 2:36 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative

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

> It may also allow a > lower barrier for contributors interested in helping with specifically > build/test infrastructure. Good point for new repo. Thanks!

Re: Cassandra Mutation object decoding

Have you explored the QueryProcessor interface? That is a legitimate extension point and may be a more suitable layer at which to integrate. On Wed, Nov 23, 2016 at 1:59 PM, Sanal Vasudevan wrote: > Hi Bejamin, > > Nice to hear from you. > > My goal is to reconstruct the CQL

Re: Cassandra Mutation object decoding

> I must say that it is really encouraging to get your thoughts. > Thanks a ton Benjamin, Jacques-Henri, Jordan Nate and Chris. > > I do not have access on the client side where the CQL is executed. QueryHandler (I called it QueryProcessor incorrectly in my initial reply) is server side:

Re: Status of dtest donation?

Not sure where we got with the ICLA (and I think filling out the paperwork fell off my plate while we were waiting to hear about that). I'll finish getting the forms together for the Incubator (again, incubation folks also handle review, we don't need to "incubate" dtest) since that was on me.

Re: STCS in L0 behaviour

> The reason is described here: https://issues.apache.org/jira/browse/CASSANDRA-5371?focusedCommentId=13621679=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13621679 > > /Marcus "...a lot of the work you've done you will redo when you compact your now bigger L0 sstable

Board report and feedback from such.

moving us forward. -Nate Attachment G: Report from the Apache Cassandra Project [Nate McCall] ## Description: The past couple of months have been difficult for us. For posterity, the August [0] and September[1] board agendas provide details of changes affecting the project and subsequent

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

To sum up that other thread (I very much appreciate everyone's input, btw), here is an aggregate list of large, breaking 4.0 proposed changes: CASSANDRA-9425 Immutable node-local schema CASSANDRA-10699 Strongly consistent schema alterations -- CASSANDRA-12229 NIO streaming CASSANDRA-8457 NIO

Re: Rough roadmap for 4.0

ed if 4.0 comes out before > February/March and 3.13/3.14. Nor do I think it’s an issue. > > — > AY > > On 16 November 2016 at 00:39:03, Mick Semb Wever (m...@thelastpickle.com) > wrote: > > On 4 November 2016 at 13:47, Nate McCall <zznat...@gmail.com> wrote: > > &g

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

+1 On Sat, Nov 19, 2016 at 7:08 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative >

Re: [VOTE] Release Apache Cassandra 3.10

+1 On Tue, Nov 1, 2016 at 2:18 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: a3828ca8b755fc98799867baf07039f7ff53be05 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative >

Re: [VOTE] Release Apache Cassandra 3.0.10

+1 On Tue, Nov 1, 2016 at 3:12 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 817ba038783212b716f6981b26c8348ffdc92f59 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative >

Re: [VOTE] Release Apache Cassandra 3.0.10

think. On Thu, Nov 3, 2016 at 2:03 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: > +1 > > On Mon, Oct 31, 2016 at 6:29 PM, Nate McCall <zznat...@gmail.com> wrote: > >> +1 >> >> On Tue, Nov 1, 2016 at 3:12 AM, Michael Shuler <mich...@pbandjelly.org>

Re: [VOTE] Release Apache Cassandra 3.10

Sorry all. Changing my vote to -1 per my comment: https://issues.apache.org/jira/browse/CASSANDRA-12867?focusedCommentId=15630442=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15630442 This pattern is more common in the wild than you might think. On Tue, Nov 1, 2016 at

Rough roadmap for 4.0

It was brought up recently at the PMC level that our goals as a project are not terribly clear. This is a pretty good point as outside of Jira 'Fix Version' labelling (which we actually suck less at compared to a lot of other ASF projects) this really isnt tracked anywhere outside of general

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

Hi Boris, Did you see this section on the site: http://cassandra.apache.org/doc/latest/development/ide.html#setting-up-cassandra-in-intellij-idea I've not had a problem setting everything up in IntelliJ following that process. On Wed, Nov 2, 2016 at 3:04 AM, BORIS MELAMED

Re: streaming_connections_per_host - speeding up CPU bound bootstrap

I have not dug too deeply yet, but how would you compare/reconcile your proposed changes with this comment: https://issues.apache.org/jira/browse/CASSANDRA-4663?focusedCommentId=15342248=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15342248 On Thu, Dec 8, 2016 at 4:10

Re: Per blockng release on dtest

> > I concede it would be fine to do it gradually. Once the pace of issues > introduced by new development is beaten by the pace at which they are > addressed I think things will go well. So from Michael's JIRA query:

Per blockng release on dtest

I'm not sure I understand the culmination of the past couple of threads on this. With a situation like: http://cassci.datastax.com/view/cassandra-3.11/job/cassandra-3.11_dtest/lastCompletedBuild/testReport/ We have some sense of stability on what might be flaky tests(?). Again, I'm not sure what

Re: [VOTE] Release Apache Cassandra 3.10 (Take 4)

> I propose the following artifacts for release as 3.10. > +1 Thanks!

Re: [VOTE] 3.X branch feature freeze

+1 Thanks for bringing this up. On Sat, Jan 14, 2017 at 6:21 AM, Aleksey Yeschenko wrote: > Hi all! > > It seems like we have a general consensus on ending tick-tock at 3.11, and > moving > on to stabilisation-only for 3.11.x series. > > In light of this, I suggest immediate

Re: Wrapping up tick-tock

> > If this question is to outside the topic and more appropriate for a > different thread I'm happy to put a hold on it until the release cadence is > agreed. > Let's please do put this on another thread. Thanks for bringing it up though as it is important and needs discussion.

Re: Per blockng release on dtest

> Seems like we'd just release that as 3.10.1 (instead of 3.11) and just > tell people "you can upgrade to 4.0 w/latest version of 3.10". This > does violate the "even releases features, odd releases bugfix", so > maybe a 3.11 as final 3.X line would help keep that consistent? This feels like a

Re: Wrapping up tick-tock

> I agreed with you at the time that the yearly cycle was too long to be > adding features before cutting a release, and still do now. Instead of > elastic banding all the way back to a process which wasn't working before, > why not try somewhere in the middle? A release every 6 months (with >

Re: Per blockng release on dtest

> > So 3.11 after 3.10, then move on to 3.11.x further bug fix releases? > +1

Re: Collecting slow queries

> That’s great. I had no idea that ticket existed. > Wow. Same. Thanks, Yoshi!

Re: [VOTE] self-assignment of jira tickets

+1

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

I don't want to lose track of the original idea from François, so let's do this formally in preparation for a vote. Having this all in place will make transition to new testing infrastructure more goal-oriented and keep us more focused moving forward. Does anybody have specific

Re: [VOTE] Release Apache Cassandra 3.0.13

On Wed, Apr 12, 2017 at 6:59 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.13. > > sha1: 91661ec296c6d089e3238e1a72f3861c449326aa +1

Re: Weekly Cassandra Wrapup

Hi Cindy, Please send an email to dev-unsubscr...@cassandra.apache.org to remove yourself from this list. Thanks, -Nate On Tue, Apr 11, 2017 at 8:07 AM, Cindy Wang wrote: > unsubscribe >

Re: Cassandra on RocksDB experiment result

> Please take a look and let me know your thoughts. I think the biggest > latency win comes from we get rid of most Java garbages created by current > read/write path and compactions, which reduces the JVM overhead and makes > the latency to be more predictable. > I want to put this here for the

Re: [VOTE] Release Apache Cassandra 3.0.12

+1 On Wed, Mar 8, 2017 at 5:15 AM, Michael Shuler 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 > a few fixes committed since 3.0.11. > > sha1:

Cassandra dtest cloned to ASF

https://github.com/apache/cassandra-dtest History is intact, but I left all the branches as that all looked like a bunch of one-off personal stuff. DataStax folks - what do y'all want to do re: "repository has moved" readme or similar? Tracking this under:

Re: State of Materialized Views

> > We're working on the following MV-related issues in the 4.0 time-frame: > CASSANDRA-13162 > CASSANDRA-13547 Patch Available > CASSANDRA-13127 Patch Available > CASSANDRA-13409 Patch Available > CASSANDRA-12952 Patch Available > CASSANDRA-13069 > CASSANDRA-12888

Re: State of Materialized Views

> > so perhaps the real solution is we need to be more aggressive about > nominating and electing committers who are willing to spend some attention on > MVs. > I am very much +1 on this solution. Huge thanks to Kurt for the excellent summarization and to Benjamin and ZhaoYang for all their

Re: Way to unsubscribe from mailing lists

> Is anyone opposed to including a footer on all the > *@cassandra.apache.org lists? I think this could be helpful. > > I've appended a default-ish ezmlm "trailer text" that I found in a doc. > > -- > Kind regards, > Michael > > --- > To

Re: Integrating vendor-specific code and developing plugins

> This being said, I don't think we should remove support for Windows or > those snitches. Instead, what I think would be more beneficial, and > certainly more reflecting the Apache Way, is to see if someone in the > community would be willing to maintain those components. Looking at another >

Re: Integrating vendor-specific code and developing plugins

> It may be better to figure out how to foster a plugin ecosystem, which is a > bit better than "there's an API go deal with it". This is what Spark is > doing and it seems like a pretty reasonable approach to me: > https://spark-packages.org/ > In thinking about this a bit, we have: Mesos, Beam

Re: Definition of QUORUM consistency level

ency. > You are write about strong consistency with that calculation, but if I want to issue a QUORUM read just by itself, I would expect a majority of nodes to reply. How it was written might be immaterial to my use case of reading 'from a majority.' -- --------- Nate McCall Wellington,

  1   2   3   >