Re: Dumb question: where is v. 0.7?

to the server. Does a clock's position on such a list correlate to a node's position on the ring? --sriram. On Jul 2, 2010, at 11:45 AM, Jeremy Hanna wrote: It's still trunk. 0.7 hasn't been tagged for a beta release or anything yet. On Jul 1, 2010, at 11:10 PM, Sriram Srinivasan sri

Re: interest in minor contention issues?

Are you talking about a handful of issues or a large number of issues? If it's the former, then a Jira issue for each isn't unreasonable. If it's the latter, maybe all of your results could go into one Jira issue with steps to reproduce your results. Then someone could do some more

Re: docs about the secondary index?

this should probably be a question on u...@cassandra, but check out this email thread from the user list: http://www.mail-archive.com/u...@cassandra.apache.org/msg05668.html On Sep 2, 2010, at 10:20 AM, Changjiu Jin wrote: Hello, Where can we find docs about the secondary index?

Re: [DISCUSSION] High-volume counters in Cassandra

Is there any feedback from Twitter and Digg and perhaps SimpleGeo people about CASSANDRA-1546? Would that work so that you wouldn't have to maintain a fork? On Sep 27, 2010, at 5:25 AM, Sylvain Lebresne wrote: In CASSANDRA-1546, I propose an alternative to #1072. At it's core, it rewrites

Re: Coordinated testing for 0.7

already making it solid. Just trying to brainstorm ways to get some additional good contributions in the core for making for a more solid 0.7.0 release. Again... any thoughts? On Dec 1, 2010, at 3:24 PM, Jeremy Hanna wrote: I was wondering if there was a coordinated plan for testing the 0.7

Re: Coordinated testing for 0.7

that there are still dragons in the node movement code. That is the primary place I would like to see more testing. On Wed, Dec 1, 2010 at 3:24 PM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: I was wondering if there was a coordinated plan for testing the 0.7 release. I realize

Re: Reducing confusion around client libraries

Including the client-dev list for thoughts/ideas. On Dec 3, 2010, at 11:43 AM, Jonathan Ellis wrote: The status quo is not working. There are way too many questions on the user list and on irc about problems with writing Thrift code, even when well-maintained clients exist for their language

Re: [VOTE] 7.0

+1 non-for-reals-binding. I did some sanity checks wrt the word count example and the pig example script on one node (with pig 0.7 and 0.8) to make sure everything was fine there with the hadoop integration in that limited context. On Jan 6, 2011, at 11:17 AM, Eric Evans wrote: RC 4 seems

Re: Avro in the Cassandra core

On Jan 17, 2011, at 9:01 PM, Eric Evans wrote: On Mon, 2011-01-17 at 12:12 -0500, Jake Luciani wrote: Some context: We have begun the process of removing Avro from the service layer CASSANDRA-926. We currently use Avro for schema migrations internally, and we have two open items that are

Re: [VOTE] 0.7.1 (3 times the charm?)

Just wondering - how does the distributed test framework fit into votes? Does it get run each time a vote happens to check for bugs/regressions? On Feb 4, 2011, at 1:40 PM, Eric Evans wrote: Lather. Rinse. Repeat. Ya'll know the drill. SVN:

Re: New feature / educational project

I think the plugins/triggers/coprocessors is a great discussion to get going again if there is interest. It's been on the to-do list for a long time and just from what I've heard anecdotally, there is a lot of interest. On Feb 8, 2011, at 3:57 PM, David G. Boney wrote: Hi All, I am also

Re: plugins/triggers/coprocessors

execution. We guarantee at least once execution in case of node failures. Cheers, Maxim On Thu, Feb 10, 2011 at 8:45 AM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: Hey guys, I was just wondering if it would be a good time to unify discussions on plugins/triggers/coprocessors

Re: plugins/triggers/coprocessors

forward with 1311: we won't be hurting anyone's feelings, and the implementation from 1016 is: 1. much, much less complete, 2. abandoned. On Fri, Feb 11, 2011 at 9:23 AM, Jeremy Hanna jeremy.hanna1...@gmail.comwrote: Thanks Maxim - I'll just go ahead and BCC you and Hentschel and move

Re: Maintenance releases

strong unbinding +1 :) I think that there were several lessons learned in the 0.6.x line about walking that line. Wrt regression testing, hopefully the distributed tests (thanks Stu and Kelvin and others!) will act as a core for something like that. I would imagine that heavy loads can be

Re: plugins/triggers/coprocessors

/CASSANDRA-1311 On Feb 11, 2011, at 1:31 PM, Jeremy Hanna wrote: So from here I guess it's a matter of working out the comments/concerns presented on 1311 and any future discussion sounds like it belongs there. Like I said, I just wanted to initiate discussion since it had been a while

Re: [VOTE] 0.7.3

We'd really like to see the updated fix for CASSANDRA-2255 get in there as well, if possible. It's very isolated to the Hadoop output code, so it shouldn't be much risk. https://issues.apache.org/jira/browse/CASSANDRA-2255 On Feb 28, 2011, at 5:27 PM, Jonathan Ellis wrote: I'd like to get

current stable

As 0.8 approaches final status in the next few weeks, I wondered about how releases receive the label, current stable. I don't know if there's any precedent for this, but I thought it might be nice to do a separate vote when new major releases are out and weigh heavily those in the community

Re: [VOTE] Release Apache Cassandra 0.7.5

+1 nonbinding On Apr 22, 2011, at 12:17 PM, Sylvain Lebresne wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts:

Re: [VOTE] Release Apache Cassandra 0.8.0 (take #3)

+1 non-binding fwiw - I ran some basic pig scripts that I have with 0.8 and they worked fine including using a UDF, filtering data, and outputting to Cassandra. - I also tried the pig and word_count examples in the src download. For some reason the cassandra output reducer didn't output

Re: [VOTE] Release Apache Cassandra 0.8.0 (take #3)

On May 31, 2011, at 5:16 PM, Edward Capriolo wrote: On Tue, May 31, 2011 at 5:42 PM, Jeremy Hanna jeremy.hanna1...@gmail.comwrote: +1 non-binding fwiw - I ran some basic pig scripts that I have with 0.8 and they worked fine including using a UDF, filtering data, and outputting

Re: Cassandra 1.0

+1 on a plan and we're excited for 1.0 because that hopefully means that Cassandra-1600 and friends will be resolved so that we can mapreduce over subsets of rows and over secondary indexes. On Jun 16, 2011, at 9:36 AM, Sylvain Lebresne wrote: Ladies and Gentlemen, Cassandra 0.8 is now out

range ghosts and more with hadoop support (with proposed solution)

We think we're running into a situation where we've deleted all the columns on several thousand rows but they still show up in the results of our pig scripts. We think that's a product of range ghosts because ColumnFamilyRecordReader uses getRangeSlices. So that might be a problem for people

404 for the download link of 0.7.6-2 src

Not sure how long this has been the case, but the download link for 0.7.6-2 src 404s on several servers: http://www.apache.org/dyn/closer.cgi?path=/cassandra/0.7.6/apache-cassandra-0.7.6-2-src.tar.gz

Re: [VOTE] Release Apache Cassandra 0.7.7

if 2870 involves all reads to LOCAL_QUORUM, then I think that would be something to include. I tried a simple pig row count using LOCAL_QUORUM today and got consistent UnavailableExceptions, but QUORUM worked. On Jul 7, 2011, at 10:14 AM, Sylvain Lebresne wrote: I propose the following

Re: Announcements List

I think a lot of people follow cassandra on twitter. However I don't think it would be a big deal to email both user@ and announcements@ when a new release is out, if people don't mind the extra list. Nick - is this from people asking about this? On Jul 18, 2011, at 9:50 AM, Gary Dusbabek

Re: set rpc_timeout_in_ms via jmx?

as an option as well. Do you want to create that ticket? jmx related ticket: https://issues.apache.org/jira/browse/CASSANDRA-2940 On Jul 18, 2011, at 11:56 AM, Ryan King wrote: On Sat, Jul 16, 2011 at 12:30 PM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: I don't see a way

moin wiki: ACLs give us no more textchas and re-enable images

I asked in #asfinfra whether images could be added now that there are pretty obscure questions for the wiki textcha questions. Their response: no. It would require another level of security. So they suggested ACLs as described in http://wiki.apache.org/general/OurWikiFarm Basically the

Re: How is Cassandra being used?

Sounds like it would be best if it were in a separate jar for people? On Nov 16, 2011, at 4:58 PM, Bill wrote: Thoughts? We'll turn this off, and would possibly patch it out of the code. That's not to say it wouldn't be useful to others. Bill On 15/11/11 23:23, Jonathan Ellis

Discussion: release quality

I'd like to start a discussion about ideas to improve release quality for Cassandra. Specifically I wonder if the community can do more to help the project as a whole become more solid. Cassandra has an active and vibrant community using Cassandra for a variety of things. If we all pitch in

Re: 1.1 freeze approaching

I like this part of that thread (w00t for a distributed test suite): # Automate all tests I think the only way that we can keep people close to trunk and stay stable is to build automated tests for *everything*. All code should be exercised by thorough unit tests and distributed black-box

Re: Document storage

I don't speak for the project, but you might give it a day or two for people to respond and/or perhaps create a jira ticket. Seems like that's a reasonable data type that would get some traction - a json type. However, what would validation look like? That's one of the main reasons there are

Re: [VOTE] Release Apache Cassandra 1.1.12

Cassandra-5488 needed an adjusted fix for reading wide rows with Pig. On 22 May 2013, at 10:07 AM, Sylvain Lebresne sylv...@datastax.com wrote: I propose the following artifacts for release as 1.1.12. sha1: 0db94069550b9c38b9f749e2087b196bb519664e Git:

Re: [VOTE] Release Apache Cassandra 1.1.12

Ah just saw Brandon's comment earlier. Sorry for the spam. On 22 May 2013, at 11:11 PM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: Cassandra-5488 needed an adjusted fix for reading wide rows with Pig. On 22 May 2013, at 10:07 AM, Sylvain Lebresne sylv...@datastax.com wrote: I propose

Re: Configuration of network connectors

Have you seen https://github.com/pcmanus/ccm as described in http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local-cassandra-clusters or does that not fit your use case? On 9 Jul 2013, at 14:02, Łukasz Dywicki l...@code-house.org wrote: Hello, First of all I would like

Re: Implementing a driver for cassandra native protocol v2

Also, you might see if you could join efforts with Aleksey on https://github.com/iamaleksey/seestar as well :) Or at least exchange ideas. On 28 Oct 2013, at 14:17, Sylvain Lebresne sylv...@datastax.com wrote: On Sat, Oct 26, 2013 at 8:07 PM, Mathieu D'Amours math...@damours.orgwrote:

Re: Refactoring cassandra service package

There was some hope started in CASSANDRA-6881 - see some of the later comments: https://issues.apache.org/jira/browse/CASSANDRA-6881 On 4 Jun 2014, at 04:04, Brian O'Neill b...@alumni.brown.edu wrote: Interesting proposition. We¹ve embedded Cassandra a few times, so I¹d be interested in an

Re: Requiring Java 8 for C* 3.0

There’s no reason why people can’t run java 8 with 2.1. IIRC the only issue we’d had with it was Dave’s https://issues.apache.org/jira/browse/CASSANDRA-7028. That’s probably the best thing for people to do though - run java 8 with 2.1 so the jump to 3.0 isn’t as significant. Good point.

Re: Cassandra Java Driver and DataStax

> On Jun 5, 2016, at 4:33 PM, Mattmann, Chris A (3980) > wrote: > > Thanks for the info Jonathan. I think have assessed based on > the replies thus far, my studying of the archives and > commit and project history the following situation. > > Unfortunately it

Re: Short column names

It has been talked about in the past, see https://issues.apache.org/jira/browse/CASSANDRA-4175 for example. However with https://issues.apache.org/jira/browse/CASSANDRA-8099, the duplication of column names is gone. So once you’re on Cassandra 3+, this optimization is a lot less valuable. >

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

Regarding high level linking, if I’m in irc or slack or hipchat or a mailing list thread, it’s easy to reference a Jira ID and chat programs can link to it and bots can bring up various details. I don’t think a hash id for a mailing list is as simple or memorable. A feature of a mailing list

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

project. > On Aug 15, 2016, at 1:27 PM, Chris Mattmann <mattm...@apache.org> wrote: > > s/dev list followers// > > That’s (one of) the disconnect(s). It’s not *you the emboldened, powerful > PMC* > and then everyone else. > > > On 8/15/16, 11:25 AM, "

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

I think a separate mailing list for just ticket creation would be nice as well. I think that’s what many of us filter down the commits@ list to. That doesn’t have to happen in place of the proposed change but would make it easier for people to follow new issue creation. From there I go to

Re: Truncate operation not available in Mutation Object

Everything in that table is deleted. There's no mutation or anything in the commitlog. It's a deletion of all the sstables for that table. To make sure everything is gone, it first does a flush, then a snapshot to protect against a mistake, then the truncate itself. > On Feb 22, 2017, at 6:05

Re: Truncate operation not available in Mutation Object

t such a truncate operation was performed on the >> table? Does it leave a trace that the truncate happened anywhere? >> >> >> Best regards, >> Sanal >> >> On Thu, Feb 23, 2017 at 11:47 AM, Jeremy Hanna <jeremy.hanna1...@gmail.com >>> >>

Re: Proposal: create a mailing list for just the newly created Jira ticket notifications

> >>> Russ >>> >>> On Mon, Aug 29, 2016 at 10:45 AM, Jonathan Haddad <j...@jonhaddad.com> >>> wrote: >>> >>>> A daily digest of new issues would be incredible. A non-binding +1 >> from >>>> this guy. >>>

Re: Proposal - 3.5.1

Right - I think like Jake and others have said, it seems appropriate to do something at this point. Would a clearer, more liberal backport policy to the odd versions be worthwhile until we find our footing? As Jeremiah said, it does seem like the big bang 3.0 release has caused much of the

Re: Support Multi-Tenant in Cassandra

I agree that the request scheduler should probably be deprecated and removed unless someone wants to put in something that's usable from the non thrift request processor. We added it for prioritization and QoS but I don't know of anyone ever using it. Our project we thought of using it for got

Re: Support Multi-Tenant in Cassandra

l-informed pros/cons of why we as a community choose to not do it, > postpone for later, or actually do it. Of course, it would be great for a > motivated individual to lead the effort if we really want to entertain it. > > On Friday, September 9, 2016, Jeremy Hanna <jeremy.hanna1...@

Proposal: create a mailing list for just the newly created Jira ticket notifications

Currently we have a mailing list (commits@) that includes commit messages as well as all updates to Jira tickets. However for the purpose of staying up to date with new tickets, it’s something of a firehose with the rapid rate of change. Some people (like me) filter out just the new ticket

Re: DataStax role in Cassandra and the ASF

Nov 5, 2016, at 10:02 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Which is what was done: https://whimsy.apache.org/board/minutes/Cassandra.html > >> On Nov 5, 2016, at 10:48 AM, Jeremy Hanna <jeremy.hanna1...@gmail.com> wrote: >> >> If the ASF is at risk

Re: DataStax role in Cassandra and the ASF

Ultimately it doesn't matter now. The project has a bright future with the involvement of all individuals regardless of the company they work for. That's the important thing. > On Nov 5, 2016, at 10:30 AM, Jeremy Hanna <jeremy.hanna1...@gmail.com> wrote: > > No it wasn't

Re: DataStax role in Cassandra and the ASF

If the ASF is at risk with a single company allowed to dominate a project then why couldn't the approach have been something like: "great job on building a successful project and community. We think there is great potential for more involvement at the core contribution level. How can we work

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

Regarding low hanging fruit, on the How To Contribute page [1] we’ve tried to keep a list of lhf tickets [2] linked to help people get started. They are usually good starting points and don’t require much context. I rarely see duplicates from lhf tickets. Regarding duplicates, in my

Re: DataStax role in Cassandra and the ASF

t any qualification :) Kind regards, Jeremy > On Nov 4, 2016, at 10:58 PM, Jeremy Hanna <jeremy.hanna1...@gmail.com> wrote: > > Hi Łukasz, > > I’m sorry you found the projects difficult to work with. It sounds like in > this case it was about modularizing with Maven and ma

Re: DataStax role in Cassandra and the ASF

Hi Łukasz, I’m sorry you found the projects difficult to work with. It sounds like in this case it was about modularizing with Maven and making TinkerPop work better with OSGI. People in the project have been going back and forth about the build process since before Riptano and DataStax

Re: Low hanging fruit crew

; 1) There’s a lot of low hanging tickets that would benefit from >> outside >>>>> contributors as their first-patch in Cassandra (like >>>>> https://issues.apache.org/jira/browse/CASSANDRA-12541 , >>>>> https://issues.apache.org/jira/browse/CASSANDRA

Re: Low hanging fruit crew

And just to be clear, I think everyone would welcome more testing for both regressions of new code correctness. I think everyone would appreciate the time savings around more automation. That should give more time for a thoughtful review - which is likely what new contributors really need to

Re: Rollback procedure for Cassandra Upgrade.

See the comment thread on https://issues.apache.org/jira/browse/CASSANDRA-8928 (add downgradesstables) > On Jan 10, 2017, at 5:00 AM, Jonathan Haddad wrote: > > There's no downgrade procedure. You either upgrade or you

Re: [VOTE] self-assignment of jira tickets

+1 non-binding. I’ve always wondered why that restriction was in place. > On Mar 29, 2017, at 8:21 AM, Jason Brown wrote: > > Hey all, > > Following up my thread from a week or two ago ( >

Re: Code quality, principles and rules

https://issues.apache.org/jira/browse/CASSANDRA-7837 may be some interesting context regarding what's been worked on to get rid of singletons and static initialization. > On Mar 17, 2017, at 4:47 PM, Jonathan Haddad wrote: > > I'd like to think that if someone refactors

Re: unsubscribe

To unsubscribe, send an email to dev-unsubscr...@cassandra.apache.org . Replying to this email does not unsubscribe you from any list. It simply perpetuates a long thread of useless emails. > On Apr 10, 2017, at 9:30 AM, Asanka Samaraweera

Re: Contribute to the Cassandra wiki

The moinmoin wiki was preferred but because of spam, images couldn’t be attached. The options were to use confluence or have a moderated list of individuals be approved to update the wiki. The decision was made to go with the latter because of the preference to stick with moinmoin rather than

Re: Contribute to the Cassandra wiki

The moinmoin wiki was preferred but because of spam, images couldn’t be attached. The options were to use confluence or have a moderated list of individuals be approved to update the wiki. The decision was made to go with the latter because of the preference to stick with moinmoin rather than

Re: Proposal to retroactively mark materialized views experimental

At the risk of sounding redundant it sounds like for MVs at this point we want to preserve current functionality for existing users. We would have a flag in the yaml to disable it by default for new MV creation with an error message. In addition we want a warning in the log and in cqlsh upon

Re: Improve the performance of CAS

Hi Dikang, Have you seen Blake’s work on implementing egalitarian paxos or epaxos*? That might be helpful for the discussion. Jeremy * https://issues.apache.org/jira/browse/CASSANDRA-6246 > On May 16, 2018, at 3:37 PM, Dikang Gu wrote: > > Hello C* developers, > > I'm

Re: Testing 4.0 Post-Freeze

e for 4.0 which will make it more successful? > > Not branching is one idea but we should discuss what will change now than > iterating what has already happened. > > On Mon, Jul 9, 2018 at 11:25 AM Jeremy Hanna > wrote: > >> I wholeheartedly agree with efforts to make release

Re: Testing 4.0 Post-Freeze

I wholeheartedly agree with efforts to make releases more stable and the more contributors that add tests or test within the context of their own use cases, the better. +1 non-binding to the idea of better, more complete testing for releases. When it comes to how to do this, I think that’s

Re: Roadmap for 4.0

On Wed, Apr 4, 2018 at 7:50 PM, Michael Shuler wrote: > On 04/04/2018 07:06 PM, Nate McCall wrote: > > > > It feels to me like we are coalescing on two points: > > 1. June 1 as a freeze for alpha > > 2. "Stable" is the new "Exciting" (and the testing and dogfooding > >

Re: Deprecating/removing PropertyFileSnitch?

age it >>>>>>>> across multiple nodes, as pointed out by Sean Durity on CASSANDRA-10745 >>>>>>>> (which is also it's Achilles' heel). To keep this ability, we could >>>>> make >>>>>>&

Re: Deprecating/removing PropertyFileSnitch?

> On Oct 29, 2018, at 11:20 AM, Jeff Jirsa wrote: > > On Mon, Oct 29, 2018 at 8:35 AM Jeremy Hanna > wrote: > >> Re-reading this thread, it sounds like the issue is there are times when a >> field may go missing in gossip and it hasn’t yet been tracked down. As &

Re: [DISCUSS] changing default token behavior for 4.0

I agree that it should be lowered. What I’ve seen debated a bit in the past is the number but I don’t think anyone thinks that it should remain 256. > On Sep 21, 2018, at 7:05 PM, Jonathan Haddad wrote: > > One thing that's really, really bothered me for a while is how we default > to 256

Re: JIRA Workflow Proposals

Regarding labels, I am personally a fan of both - the mapping of commonly used labels to things like components, features, tools, etc. as well as keeping labels for newer and more arbitrary groupings. I’ve tried to maintain certain labels like virtual-tables, lcs, lwt, fqltool, etc because

Re: [VOTE] Accept GoCQL driver donation and begin incubation process

I don’t know if others have this same question, but what does accepting the gocql driver donation mean? It becomes a full Apache project separate from Cassandra and there exists a separate set of PMC members and such? Or does it become part of the Cassandra project itself? From Sylvain and

Re: Contributing cassandra-diff

It’s great to contribute such a tool. The change between 2.x and 3.0 brought a translation layer from thrift to cql that is hard to validate on real clusters without something like this. Thank you. As for naming, perhaps cassandra-compare might be clearer as diff is an overloaded word but

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

(non-binding) +1 Speaking of the testing, thanks all for the different tooling and test runs. Things like fqltool, cassandra-diff, and the testing that Joey has been doing with https://issues.apache.org/jira/browse/CASSANDRA-14747 are

Re: Update defaults for 4.0?

We should also update our JVM defaults. > > On Thu, Jan 23, 2020, 9:28 PM Jeremy Hanna > wrote: > > > To summarize this thread, I think people are generally okay with updating > > certain defaults for 4.0 provided we make sure it doesn't unpleasantly > > sur

Re: Update defaults for 4.0?

yments, and for real production we need to use >GossipingPropertyFileSnitch - why not to set it as default? > > > Jeremy Hanna at "Wed, 22 Jan 2020 11:22:36 +1100" wrote: > JH> I mentioned this in the contributor meeting as a topic to bring up on > the list -

Re: [Discuss] num_tokens default in Cassandra 4.0

t; Thanks for restarting this discussion Jeremy. I personally think 4 is a >>> good number as a default. I think whatever we pick, we should have enough >>> documentation for operators to make sense of the new defaults in 4.0. >>> >>> Dinesh >>> >&g

Re: [Discuss] num_tokens default in Cassandra 4.0

I think Mick and Anthony make some valid operational and skew points for smaller/starting clusters with 4 num_tokens. There’s an arbitrary line between small and large clusters but I think most would agree that most clusters are on the small to medium side. (A small nuance is afaict the

[Discuss] num_tokens default in Cassandra 4.0

I wanted to start a discussion about the default for num_tokens that we'd like for people starting in Cassandra 4.0. This is for ticket CASSANDRA-13701 (which has been duplicated a number of times, most recently by me). TLDR, based on

Update defaults for 4.0?

I mentioned this in the contributor meeting as a topic to bring up on the list - should we take the opportunity to update defaults for Cassandra 4.0? The rationale is two-fold: 1) There are best practices and tribal knowledge around certain properties where people just know to update those

Re: Update defaults for 4.0?

wrong). > > > > I'm sure there are others that would be safe to change. I'll review our > > defaults we typically set and report back tomorrow. > > > > On Tue, Jan 21, 2020, 7:22 PM Jeremy Hanna > > wrote: > > > > > I mentioned this in t

Re: [Discuss] num_tokens default in Cassandra 4.0

As discussed, let's go with 16. Speaking with Anthony privately as well, I had forgotten that some of the analysis that Branimir had initially done on the skew and allocation may have been internal to DataStax so I should have mentioned that previously. Thanks to Mick, Alex, and Anthony for

Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

Thanks Adam. Now that we have CASSANDRA-16079 created and work is proceeding, can we please commit CASSANDRA-13701? There are many clusters out there that use the default of 256 num_tokens and migrating to something more sane is a lot of work. It would also be very helpful for having

Re: Supported upgrade path for 4.0

So to reiterate the recommended/tested paths that I get from this thread: 2.1.x -> 2.1.latest -> [3.0.latest | 3.11.latest] -> 4.0 2.2.x -> 2.2.latest -> [3.0.latest | 3.11.latest] -> 4.0 3.0 -> 3.0.latest -> 4.0 3.x -> 3.11.latest -> 4.0 I just wanted to be explicit about getting to the latest

Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

I know the dtests take a long time and this will make them longer. As a counter point most people run individual dtests locally and the full set on dedicated test infrastructure. For the dedicated test infrastructure Mick also improved the wall clock runtime when parallelizing the dtests on

Re: Update defaults for 4.0?

; > Since I planned on experimenting with the whole "what does the confluent > > testing page look like in an epic" today, I'll ping Nate once it's not > > godawfully early in NZ about this. Or he'll read this email, either way. > :) > >

Re: [Discuss] num_tokens default in Cassandra 4.0

with num_tokens: 16. There is a note in the NEWS.txt about upgrading and bootstrapping. It is a lot of effort to change this once it is set, so hopefully new users will be in a much better place out of the box. Thanks everyone for your efforts in this. On Wed, Apr 1, 2020 at 4:28 PM Jeremy Hanna wrote

Moving forward towards our best release yet

I've been in the Cassandra community for about 10 years now and I've seen a lot of ups and downs. I care deeply about both the project and the people interacting on the project personally. I consider many of you to be good friends. Regardless of the history that's caused some friction on

Re: [VOTE] Project governance wiki doc (take 2)

> On Jun 25, 2020, at 10:56 AM, Jordan West wrote: > > On Wed, Jun 24, 2020 at 3:43 PM Dinesh Joshi wrote: > >> 3. Discussion #3 - "... 1 business day notice period." Whose business day >> is it? US? Europe? Australia? NZ? We are a distributed community and so 1 >> business day is

Re: Welcome Caleb Rackliffe as Cassandra committer

Congratulations Caleb! > On May 14, 2021, at 11:02 PM, Mick Semb Wever wrote: > > The PMC members are pleased to announce that Caleb Rackliffe has > accepted the invitation to become committer. > > Thanks heaps Caleb for helping make Cassandra awesome! > > Congratulations and welcome, > The

Re: [VOTE] Release Apache Cassandra 4.0-rc2

+1 (nb) nice to see all of the fixes and the use of newer TLS by default and obfuscation of passwords in the audit log for the 4.0 release. > On Jun 29, 2021, at 6:01 AM, Jon Meredith wrote: > > +1 (nb) > >> On Mon, Jun 28, 2021 at 9:47 AM Yifan Cai wrote: >> >> +1 >> >> >> - Yifan >>

Re: [DISCUSSION] Attracting new contributors

One thing we've done in the past is contributor bootcamps along with the the new contributor guide and the LHF complexity tickets. Unfortunately, I don't know that the contributor bootcamps were ever recorded. Presentations were done to introduce people to the codebase generally (I think Gary

Re: [DISCUSSION] Attracting new contributors

periodic group chat to talk through one of the issues that they > may be working on together as a group with an active contributor might make > sense, and be more targeted in focus? > > > On 27/04/2021, 12:45, "Manish G" wrote: > >Contributor bootcamps can really help n

Re: [DISCUSS] CEP 14: Paxos Improvements

It sounds like a great improvement! Just for those who had followed the development of ePaxos* that Blake and others worked on but was never committed, it would be nice to briefly compare the two. https://issues.apache.org/jira/browse/CASSANDRA-6246 > On Aug 19, 2021, at 9:18 AM, Scott

Re: [DISCUSS] Java support roadmap

One of the things I'm excited about with the 4+ releases is this running with Java 17+ (including ZGC) so I would love to see this get more serious testing and validation. Anecdotal account - at an event a couple of years ago, I spoke to someone from an education software company was running

Re: [VOTE] Release Apache Cassandra 4.0.0 (take2)

+1 (nb) > On Jul 15, 2021, at 3:42 AM, Blake Eggleston > wrote: > > +1 > >> On Jul 14, 2021, at 8:21 AM, Aleksey Yeschenko wrote: >> >> +1 >> On 14 Jul 2021, at 15:37, Jonathan Ellis wrote: >>> >>> +1 >>> On Tue, Jul 13, 2021 at 5:14 PM Mick Semb Wever wrote:

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 nb On Sat, Jul 24, 2021 at 11:50 AM Scott Andreas wrote: > +1 nb > > > On Jul 23, 2021, at 2:46 PM, 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 > >>

Re: New Apache Cassandra Group on LinkedIn

Is it possible to ask someone at linkedin to merge the groups together so that it's managed by the PMC but with the explicit permission of the people running the other group? In the past, I know that Twitter does things like that in terms of handles and followers. Is that a desirable outcome?

Re: [VOTE] CEP-19: Trie memtable implementation

+1 nb. Thanks for all of the great work on this Branimir. Excited to see this moving forward. > On Feb 16, 2022, at 7:56 AM, J. D. Jordan wrote: > > +1 nb > >> On Feb 16, 2022, at 7:30 AM, Josh McKenzie wrote: >> >>  >> +1 >> >> On Wed, Feb 16, 2022, at 7:33 AM, Ekaterina Dimitrova

  1   2   >