Re: List of serious issues fixed in 3.0.x

Hi Sankalp, Thanks for bringing this up. At the very minimum, I hope we have regression tests for the specific issues we have fixed. I personally think, the project should focus on building a comprehensive test suite. However, some of these issues can only be detected at scale. We need users t

Re: Calling for release managers (Committers and PMC)

I can help out. Dinesh > On May 7, 2020, at 11:29 AM, Mick Semb Wever wrote: > > The Cassandra release process has had some improvements to better in > line with the ASF guidelines: sha256 & sha512 checksums, staged > artefacts in svnpubsub, dep and rpm repositories complete and signed > in sta

Re: Support for networking via identity instead of IP

Hi Chris, I skimmed through your proposal and it looks interesting. We can definitely discuss this but at the moment we’re iterating on releasing 4.0 so your proposal may not get a whole lot of traction. We also have a new process to propose largish changes like you suggested called CEP (Cassan

Re: [DISCUSS] CASSANDRA-13994

;>> waters. >>>>>>>>>> >>>>>>>>>> My very loosely held perspective is that beta-1 to ga is >>>> the >>>>>>>>> window in >>>>>>>>>&

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

+0 I realize this is a vote thread and I am late for feedback but I wanted to point out a couple things: 1. How/Who/Where are we planning to deal with Code of Conduct violations? I assume this should be private@ but the document does not call it out as such. We should call it out explicitly as

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

> On Jun 24, 2020, at 6:01 PM, Brandon Williams wrote: > > On Wed, Jun 24, 2020 at 5:43 PM Dinesh Joshi wrote: >> 1. How/Who/Where are we planning to deal with Code of Conduct violations? I >> assume this should be private@ but the document does not call it out as >&

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

; seems to me you are addressing here? >>> >>> Since we reference the ASF CoC, and the ASF provides its own guide for >>> handling CoC complaints (including within projects), that applies to that >>> very CoC (and which you referenced), it's unclea

Re: DataStax Driver Donation to Apache Cassandra Project

I don't see any reason not to bring in other drivers to the project. We can start with the Java driver. I think Nate might be aware of the specifics of the process. Dinesh > On Jun 25, 2020, at 11:36 AM, Joshua McKenzie wrote: > > My understanding is that there's comparable traffic on python,

Re: [DISCUSS] When to branch 4.0

> On Jun 26, 2020, at 3:45 PM, David Capwell wrote: > > the ability to test their impact. Even simple things become hard given the > fact only committers can run Jenkins tests, or you pay money to be able to > run the tests... If the intent is to make it easier for new people to > contribute to

[DISCUSS] Stabilizing 4.0

Hi all, I am starting a separate thread as the other thread has veered off in a very different direction. The ground rules for this thread are that we are not discussing branching models or release strategy here. Some folks in the community had the following questions and concerns: 1. Lack of

Re: [DISCUSS] Future of MVs

> On Jun 30, 2020, at 12:43 PM, Jon Haddad wrote: > > As we move forward with the 4.0 release, we should consider this an > opportunity to deprecate materialized views, and remove them in 5.0. We > should take this opportunity to learn from the mistake and raise the bar > for new features to und

Re: [DISCUSS] Future of MVs

> On Jun 30, 2020, at 3:27 PM, David Capwell wrote: > > If that is the case then shouldn't we add MV to "4.0 Quality: Components > and Test Plans" (CASSANDRA-15536)? It is currently missing, so adding it > to the testing road map would be a clear sign that someone is planning to > champion and o

Re: [DISCUSS] Future of MVs

> On Jun 30, 2020, at 3:40 PM, joshua.mcken...@gmail.com wrote: > > I don’t think we should hold up releases on testing experimental features. > Especially with how many of them we have. > > Given we’re at a place where things like MV’s and sasi are backing production > cases (power users one w

Re: [DISCUSS] Future of MVs

> On Jun 30, 2020, at 4:05 PM, Brandon Williams wrote: > > Instead of ripping it out, we could instead disable them in the yaml > with big fat warning comments around it. That way people already > using them can just enable them again, but it will raise the bar for > new users who ignore/miss th

Re: [DISCUSS] Stabilizing 4.0

Thank you all those who responded. One potential way we could speed up sussing out issues is running regular "Bug Bashes" with the help of the user community. We could periodically post stats and recognize folks who contribute the most issues. This would help gain confidence in the builds we're

Re: [DISCUSS] Future of MVs

> On Jun 30, 2020, at 4:52 PM, joshua.mcken...@gmail.com wrote: > > I followed up with the clarification about unit and dtests for that reason > Dinesh. We test experimental features now. I hit send before seeing your clarification. I personally feel that unit and dtests may not surface regress

Re: [NOTICE] ApacheCon talk submission voting

Hi Nate, Count me in. Happy to assist. Dinesh > On Jul 19, 2020, at 2:00 PM, Nate McCall wrote: > > Hi folks, > ApacheCon@Home Cassandra track finally coming together. We have a little > over 20 submissions to go through initially this week to put together a > rough schedule. > > This year, w

Re: [DISCUSS] CEP-8 Drivers Donation

Alexandre, I gave the document a quick read and TL;DR seems to be that we'd like to: 1. Bring in all drivers 2. They're part of the C* project If so, I would prefer if we add the Java driver first to the project. Based on that experience we can move forward with other drivers. However, I am ope

Re: [DISCUSS] Change style guide to recommend use of @Override

+1 > On Sep 1, 2020, at 11:27 AM, David Capwell wrote: > > Currently our style guide recommends to avoid using @Override and updates > intellij's code style to exclude it by default; I would like to propose we > change this recommendation to use it and to update intellij's style to > include it

Re: Creating a branch for 5.0 …?

> On Sep 10, 2020, at 2:10 PM, Joshua McKenzie wrote: > > I can offer my anecdata: I know of two major enterprises as well as have > had two interviewees unsolicited bring up to me that they have walked away > from or bounced off the project due to the feature freeze / branching > strategy. I may

Re: [VOTE] Accept the Harry donation

+1 Dinesh > On Sep 16, 2020, at 9:30 AM, Joshua McKenzie wrote: > > +1 > > >> On Wed, Sep 16, 2020 at 11:22 AM, Aleksey Yeshchenko < >> alek...@apple.com.invalid> wrote: >> >> +1 >> >> On 16 Sep 2020, at 16:09, Sumanth Pasupuleti > com> wrote: >> >> +1 (non-binding) >> >> On Wed, Sep 16,

Re: Creating a branch for 5.0 …?

Maybe you should ask these people to bring their contributions or issues directly to the dev list. You don’t need to disclose their names or contact information. Contributing to the project involves engaging the community. We’re still open to discussions even if the patches may not land immedia

Re: Creating a branch for 5.0 …?

Josh, > For what it's worth, when I engage with other people working on large forks > that want to bring their features back to the project, the absolute last > thing I want to do to them is throw them into email threads like this. People need to positively engage with the community, have discuss

Re: TLS protocol configuration for secure internode messaging needs improvement before the final 4.0 release

+1 on it. It looks like a reasonable change. Dinesh > On Oct 1, 2020, at 4:31 PM, Jon Meredith wrote: > > I didn't receive any feedback on the previous email I sent about this > on September 23rd. A couple of people pointed out the email got > flagged as suspicious so I've updated the an older

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

+1 generally. We should do this for the sidecar repo as well. Dinesh > On Oct 2, 2020, at 2:17 AM, Mick Semb Wever wrote: > > Next week I plan to rename master branches on the cassandra-builds, > cassandra-website and cassandra-dtest repositories to trunk. > > This was discussed in > https:/

Re: Welcome Jordan West, David Capwell, Zhao Yang and Ekaterina Dimitrova as Cassandra committers

Congratulations everyone! Dinesh > On Dec 16, 2020, at 8:55 AM, Benjamin Lerer > wrote: > > The PMC's members are pleased to announce that Jordan West, David Capwell, > Zhao Yang and Ekaterina Dimitrova have accepted the invitations to become > committers this year. > > Jordan West accepted

Re: Welcome Yifan Cai as Cassandra committer

Congrats Yifan! Dinesh > On Dec 21, 2020, at 9:10 AM, Benjamin Lerer > wrote: > >  The PMC's members are pleased to announce that Yifan Cai has accepted the > invitation to become committer last Friday. > > Thanks a lot, Yifan, for everything you have done! > > Congratulations and welcome

Re: Welcome Paulo Motta as Cassandra PMC member

Congratulations, Paulo! Dinesh > On Feb 9, 2021, at 7:54 AM, Benjamin Lerer > wrote: > >  The PMC's members are pleased to announce that Paulo Motta has accepted > the invitation to become a PMC member yesterday. > > Thanks a lot, Paulo, for everything you have done for the project all these

Re: Release votes

I'm new to this project and here are my two cents. If there are tests that are constantly failing or flaky and you have had releases despite their failures, then they're not useful and can be disabled. They can always be reenabled if they are in fact valuable. Having 100% blue dashboard is not i

Re: Design Proposal for Auditing feature in Cassandra

Hey Anuj, Thanks for submitting the patch. I am looking at the design. Will comment on the Jira with my feedback. Dinesh On Monday, February 26, 2018, 4:09:41 AM PST, Anuj Wadehra wrote: Hi, Apache Cassandra doesn't provides an auditing feature. As Database auditing is critical for a

Re: Timeout unit tests in trunk

Some tests might require additional resources to spin up the required components. 2 CPU / 4GB might not be sufficient. You may need to bump up the resources to 8CPU / 16GB. Dinesh On Tuesday, February 27, 2018, 11:24:34 AM PST, Dikang Gu wrote: Looks like there are a few flaky/timeou

Re: Timeout unit tests in trunk

f @resource_intensive to unit tests too.. and the first one is > to stop from running the MV unit tests in the free circleci containers. > thoughts? > > also, might want to bug your management to see if you can get some paid > circleci resources. it's game changing! &

Re: Pull request question

Hi Kenneth, Normally you would open a Jira ticket and put the details in there including a link to your branch, pull request or patch. Is this pull request associated with a jira? If so, could you please point us to it? And yes, normally you would send pull requests against trunk unless they're

Re: Paying off tech debt and correctly naming things

Having been through a bunch of refactors in other projects, I would suggest doing small incremental patches isolated in related parts of the code. It would also be nice if you could give us a heads up on changes you're making. Best of luck! Dinesh On Tuesday, March 20, 2018, 3:04:43 PM PDT,

Re: Repair scheduling tools

Simon, You could still do load aware repair outside of the main process by reading Cassandra's metrics. In general, I don't think the maintenance tasks necessarily need to live in the main process. They could negatively impact the read / write path. Unless strictly required by the serving path,

Proposing an Apache Cassandra Management process

hould not be. We are looking forward to your comments on our proposal, Dinesh Joshi and Jordan West

Re: Proposing an Apache Cassandra Management process

moving features from Priam (such as backup, HTTP -> JMX, etc) incrementally > to this sidecar as they make sense. > > > Thanks, > Vinay Chella > > On Fri, Apr 13, 2018 at 7:01 AM, Eric Evans > wrote: > > > On Thu, Apr 12, 2018 at 4:41 PM, Dinesh Joshi > &g

Re: [DISCUSS] Replace airlift/airline library with Picocli

On Tue, Jul 16, 2024 at 8:48 AM Jeff Jirsa wrote: > if it’s unmaintained, let’s remove it before we’re doing it on fire. > +1 Fire drills are never pleasant. CLI parsing isn't a huge area of personal interest to me. However, it presents a non-trivial attack surface as input processing is a rip

Re: Welcome Joey Lynch as Cassandra PMC member

Congratulations, Joey! On Wed, Jul 24, 2024 at 12:26 PM Patrick McFadin wrote: > Every once in a while you see an announcement and think "Wasn't that > already a thing?" and then realize it wasn't. This is one of those times. > Congratulations Joey on the thing I thought you already were so clea

Re: [DISCUSS] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

Any change we bring to stable releases, even though it is non-user facing change, brings in the possibility of introducing bugs and / or unintended side effects. Therefore it is important to carefully consider the trade offs when we make changes to older releases. We also have a precedent to make c

Re: [DISCUSS] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

On Tue, Jul 30, 2024 at 11:47 AM Mick Semb Wever wrote: > This also incentivises intentionally not introducing support for that api > in older mainlines. We KISS, if the user wants that ecosystem benefit they > need to upgrade to at least mainline X. > > Once older mainlines have it then we have

Re: [VOTE] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

+1 I think this is a low risk change which is going to avoid duplication of effort so it is worth it. On Sat, Aug 3, 2024 at 11:19 PM Yifan Cai wrote: > Hi, > > I am proposing backporting CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0. > > There is a discussion thread >

Re: Implement details of Protocol v5 framing

Hi Vincent, This is the Cassandra user's mailing list. You can engage the Cassandra developers on dev@cassandra.apache.org mailing list. I have bcc'd the user list and added the dev list. To answer your question, the spec may have drifted and may require a fix. Please feel free to raise a jira an

Welcome Doug Rohrer as Cassandra Committer

The Apache Cassandra PMC is thrilled to announce that Doug Rohrer has accepted the invitation to become a committer! Doug has worked on several aspects of Cassandra, Sidecar, and Analytics. Congratulations and welcome! The Apache Cassandra PMC members

Re: 【DISCUSS】The configuration of Commitlog archiving

Thanks for bringing this to the mailing list. I quickly skimmed the feature and I agree with you that having an arbitrary command executed could be dangerous. However, this is a 12 year old feature and so am guessing there are people using it. As far as locking down the feature, I don't think it i

Re: Welcome Jordan West and Stefan Miklosovic as Cassandra PMC members!

Congratulations to the both of you. Thank you for being valuable members of the Apache Cassandra community and all the hard work you have put in over the years! Dinesh On Fri, Aug 30, 2024 at 1:21 PM Jon Haddad wrote: > > The PMC's members are pleased to announce that Jordan West and Stefan > M

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

My 2c are below – We have a patch that is preventing a known data loss issue. People may or may not know they're suffering from this issue so this should go in all supported versions of Cassandra with it enabled by default. Will this cause issues for operators? Sure. Is it worth keeping this featu

Re: Welcome Chris Bannister, James Hartig, Jackson Flemming and João Reis, as cassandra-gocql-driver committers

Congratulations, everyone! On Thu, Sep 12, 2024 at 4:40 AM Mick Semb Wever wrote: > The PMC's members are pleased to announce that Chris Bannister, James > Hartig, Jackson Flemming and João Reis have accepted invitations to > become committers on the Drivers subproject. > > Thanks a lot for ever

Re: [VOTE] Release Apache Cassandra 4.0-rc1

+1 Dinesh > On Mar 29, 2021, at 1:41 PM, Nate McCall wrote: > > +1 > > >> On Tue, Mar 30, 2021 at 2:06 AM Mick Semb Wever wrote: >> >> Proposing the test build of Cassandra 4.0-rc1 for release. >> >> sha1: 2facbc97ea215faef1735d9a3d5697162f61bc8c >> Git: >> >> https://gitbox.apache.org/r

Re: [VOTE] Release Apache Cassandra 4.0-rc1 (take2)

+1 Dinesh > On Apr 22, 2021, at 1:12 PM, Ben Bromhead wrote: > > +1 (nb) > >> On Fri, Apr 23, 2021 at 2:37 AM Marcus Eriksson wrote: >> >> +1 >> >>> On Wed, Apr 21, 2021 at 08:51:23PM +0200, Mick Semb Wever wrote: >>> Proposing the test build of Cassandra 4.0-rc1 for release. >>> >>> sha1

Re: Welcome Dinesh Joshi as Cassandra PMC member

Andreas wrote: >>> >>> Congratulations, Dinesh! >>> >>> >>> From: Lorina Poland >>> Sent: Wednesday, June 2, 2021 9:27 AM >>> To: dev@cassandra.apache.org >>> Subject: Re: Welcome Dinesh

Re: [DISCUSS] CIP-9: Make SSLContext creation pluggable

Hi Maulin, Thank you for the CEP & Patch. I’ve been following along albeit silently. Will take a look. It’s just that we’re currently busy so bear with us. Thanks, Dinesh > On Jun 2, 2021, at 3:28 PM, Maulin Vasavada wrote: > > Hi all > > ^^^ bump ^^^ I've raised the PR and am waiting for

Re: Are we ready for 4.0.0 (GA) ?

Based on the release lifecycle[1], we should cut another RC until we don’t find any blocking issues. Dinesh [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132320437 > > On Jun 14, 2021, at 9:05 PM, Scott Andreas wrote: > > A second RC is appropriate given the revert of

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

+1 Dinesh > On Jul 15, 2021, at 8:01 AM, Enrico Olivelli wrote: > > +1 > > - Run all tests with CDC > - Verified checksums and digital signatures > > Enrico > >> Il giorno gio 15 lug 2021 alle ore 16:59 Branimir Lambov < >> branimir.lam...@datastax.com> ha scritto: >> >> +1 >> >> On Thu,

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

Thanks for the heads up Jon. Please ping the list once you have filed the jira. Dinesh > On Jul 16, 2021, at 5:28 PM, Jon Meredith wrote: > > -1 nb. > > I'll open a JIRA with details later tonight or first thing tomorrow. > > I've confirmed that the serialization and deserialization of FWD_

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

+1 > On Jul 23, 2021, at 4:56 AM, Paulo Motta wrote: > > +1 > >> Em sex., 23 de jul. de 2021 às 08:37, Andrés de la Peña < >> a.penya.gar...@gmail.com> escreveu: >> >> +1 >> >>> On Fri, 23 Jul 2021 at 11:56, Sam Tunnicliffe wrote: >>> >>> +1 >>> On 22 Jul 2021, at 23:40, Brandon Wil

Re: [VOTE] Release Apache Cassandra 4.0.1

+1 Dinesh > On Sep 1, 2021, at 4:54 AM, Sam Tunnicliffe wrote: > > Proposing the test build of Cassandra 4.0.1 for release. > > sha1: 6709111ed007a54b3e42884853f89cabd38e4316 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative > Maven Artifacts

Re: [DISCUSS] CEP-15: General Purpose Transactions

+1 One of the major advantages of a separate library would be modularity. Dinesh > On Sep 5, 2021, at 3:02 PM, bened...@apache.org wrote: > > Yep, that’s correct. In fact my goal is that we maintain this as a > standalone library long term. While its primary goal will be integration with > C

Re: [DISCUSS] CEP-16: Auth Plugin Support for CQLSH

Hi Brian, Thanks - the CEP looks good to me. We can move to vote. Could you please initiate it? Dinesh > On Sep 30, 2021, at 4:27 PM, bhouse99 wrote: > > Hi everyone. Are there any other thoughts or comments regarding the CEP-16: > Auth Plugin Support for CQLSH proposal? > > - > https://c

Re: [VOTE] Release dtest-api 0.0.10

+1 Dinesh > On Oct 5, 2021, at 7:27 PM, Joshua McKenzie wrote: > > +1 > >> On Tue, Oct 5, 2021 at 2:15 PM Brandon Williams wrote: >> >> +1 >> >>> On Tue, Oct 5, 2021 at 11:47 AM Oleksandr Petrov >>> wrote: >>> >>> Proposing the test build of in-jvm dtest API 0.0.10 for release. >>> >>>

Re: [DISCUSS] CASSANDRA-17024: Artificial Latency Injection

> On Oct 6, 2021, at 8:07 AM, Jonathan Ellis wrote: > > I would love to see CLs simplified. Even without user-provided CL we > almost certainly have too many. Providing a migration path is the hard > part. +1 on deprecating consistency levels. Migration path is easy for most use-cases. Some n

Re: [DISCUSS] CEP-17: Add support for PEM based key material for SSL

This could be just an enhancement jira. No need for a CEP. I think this would be a fine addition to Cassandra. Please ensure that we can support both PEM as well as the current JKS simultaneously. Dinesh > On Oct 11, 2021, at 3:06 AM, Stefan Miklosovic > wrote: > > I agree with Benedict, t

Re: [VOTE] CEP-16 - Auth Plugin Support for CQLSH

+1 > On Oct 11, 2021, at 2:50 AM, Stefan Miklosovic > wrote: > > Hi list, > > based on the discussion thread about CEP-16 (1), I would like to have > a vote on that. > > It seems to me CEP-16 is so straightforward there is more or less > nothing to discuss in more depth as the feedback it ga

Re: [DISCUSS] CASSANDRA-17031: Add support for PEM based key material for SSL

On 10/11/21 12:34 PM, Maulin Vasavada wrote: Dinesh, when you say PEM and JKS formats simultaneously, do you mean that for client vs internnode ssl we should be able to use different formats OR beyond that within particular encryption options have a combination - PEM based private keys and JKS ba

Re: [VOTE] CEP-15: General Purpose Transactions

On 10/14/21 9:31 AM, bened...@apache.org wrote: > 1. Do you support adopting this CEP? > 2. Do you support the transaction semantics proposed by the CEP for Cassandra? > 3. Do you support an incremental approach to developing transactions in > Cassandra, leaving scope for future development? +1 o

Re: [VOTE] CEP-15: General Purpose Transactions

On 10/14/21 2:07 PM, Mick Semb Wever wrote: > 1. -1 > > There's discussions still ongoing around this CEP. I support the CEP but > believe it is important that the community takes the patience to let > everyone say their piece and feel that they have been heard. I do not see > that waiting a week

Re: Tradeoffs for Cassandra transaction management

On 10/14/21 6:54 AM, Jonathan Ellis wrote: > I think I've also been clear that I want a path to supporting (1) local > latencies (SLOG is a more elegant solution but "let's just let people give > up global serializability like LWT" is also reasonable) and (2) SQL with > interactive transactions.

Re: Tradeoffs for Cassandra transaction management

block. Dinesh > On Oct 15, 2021, at 2:01 AM, Henrik Ingo wrote: > On Fri, Oct 15, 2021 at 3:37 AM Dinesh Joshi > wrote: > >>> On 10/14/21 6:54 AM, Jonathan Ellis wrote: >>> I think I've also been clear that I want a path to supporting (1) local >>> la

Re: [DISCUSS] CEP-18: Improving Modularity

> On Oct 25, 2021, at 1:22 PM, Jeremiah D Jordan wrote: > > The currently proposed changes in CEP-18 should all include improved test > coverage of the modules in question. We have been developing them all with a > requirement that all changes have at least %80 code coverage from sonar cloud

Re: [DISCUSS] Creating a new slack channel for newcomers

> On Nov 8, 2021, at 8:43 AM, Matt Kennedy wrote: > > welcome > the addition of a dev slack channel as a much more approachable forum in > which to ask stupid questions. This mailing least seems focused on Instead why don't we make cassandra-dev more approachable for new developers? If newco

Re: [VOTE] CEP-17: SSTable format API

+1 > On Nov 17, 2021, at 1:22 AM, Benjamin Lerer wrote: > > +1 > > Le mar. 16 nov. 2021 à 18:05, Joshua McKenzie a > écrit : > >> +1 >> >> On Tue, Nov 16, 2021 at 10:14 AM Andrés de la Peña >> wrote: >> >>> +1 >>> >>> On Tue, 16 Nov 2021 at 08:39, Sam Tunnicliffe wrote: >>> +1

Re: [DISCUSS] Throughput issues when inserting on contended partitions

+1 Dinesh > On Dec 1, 2021, at 5:59 AM, Mick Semb Wever wrote: > >  >> >> I am wondering if we should not consider implementing those changes in 4.0 >> considering the fact that they will fix serious existing issues and would >> like to hear your options about it. > > > +1 to see them land

Re: [DISCUSS] Non Coding Committers

Hi Sharan, Thank you for the feedback. Couple points that immediately struck me was the use of the word 'committer'. This term is closely associated with code contributions and therefore causes confusion. I understand that ASF defines it differently but it is unfortunately overloaded. Perhaps t

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

This is excellent. Thanks for opening up this CEP. It would be great to get some stats around GC allocation rate / memory pressure, read & write latencies, etc. compared to existing implementation. Dinesh > On Jan 18, 2022, at 2:13 AM, Branimir Lambov wrote: > > The memtable pluggability API

Re: Build tool

We have spent a lot of time discussing this topic than actually trying to arrive at a decision. Everyone has a strong opinion about which build tool the project should use. Each tool has its strengths and weaknesses. Today, `gradle` is the best tool for Java based projects in _my_ experience. I

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

022, at 8:39 AM, Branimir Lambov wrote: > > Added some performance results to the ticket: > https://issues.apache.org/jira/browse/CASSANDRA-17240 > <https://issues.apache.org/jira/browse/CASSANDRA-17240> > > Regards, > Branimir > > On Sat, Feb 5, 2022 a

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

; that have new performance characteristics. So I like the idea that the > proposed configuration approach which allows someone to change to a new > implementation one node at a time and only for specific tables. > >> On Feb 8, 2022, at 2:21 PM, Dinesh Joshi > <mailto:djo...

Re: [VOTE] Release Apache Cassandra 4.0.2

+1 on the release > On Feb 8, 2022, at 3:44 PM, Jeff Jirsa wrote: > > (This was a +1 on the release, to be clear, not a +1 on the sentiment below, > which I appreciate but still believe we should proceed with the release) > > > On Tue, Feb 8, 2022 at 3:44 PM Jeff Jirsa

Re: [VOTE] Release Apache Cassandra 3.0.26

+1 > On Feb 8, 2022, at 12:22 PM, Jeremiah D Jordan > wrote: > > -1 nb for same reason as I said for the 4.0.2 vote here: > https://lists.apache.org/thread/7zc22z5vw5b58hdzpx2nypwfzjzo3qbr > >

Re: [VOTE] Release Apache Cassandra 3.11.12

+1 > On Feb 8, 2022, at 12:22 PM, Jeremiah D Jordan > wrote: > > -1 nb for same reason as I said for the 4.0.2 vote here: > https://lists.apache.org/thread/7zc22z5vw5b58hdzpx2nypwfzjzo3qbr > > > >> On Feb 8, 2022, at 4:10 AM

Re: [RELEASE] Apache Cassandra 4.0.2 released

We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future. > On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova > wrote: > > Note taken, I had to document only in 4.0.x that those are placeholder. I > just opened ticket to fix that - CA

Re: [RELEASE] Apache Cassandra 4.0.2 released

> unnecessarily. > > > > I wonder if we should introduce a compile time check that validates config > compatibility with prior versions, to avoid this in future. > > > > From: Dinesh Joshi mailto:djo...@apache.org>> > Date: Saturday, 12 February 2022 at

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

+1 On 2/16/22 21:45, Berenguer Blasi wrote: > +1 > > On 16/2/22 23:50, Joseph Lynch wrote: >> +1 nb >> >> Really excited for this, Thank you Branimir! >> >> -Joey >> >> On Wed, Feb 16, 2022 at 12:58 AM Branimir Lambov >> wrote: >>> Hi everyone, >>> >>> I'd like to propose CEP-19 for approval. >>

Re: [VOTE] CEP-7: Storage Attached Index

+1 On 2/17/22 23:47, DuyHai Doan wrote: > +1 nb > > On Fri, Feb 18, 2022 at 7:41 AM Berenguer Blasi > mailto:berenguerbl...@gmail.com>> wrote: > > +1 > > On 18/2/22 2:15, Jasonstack Zhao Yang wrote: >> +1 >> >> On Fri, 18 Feb 2022 at 08:15, Jeremy Hanna >> mailto:jeremy.hann

Re: [GSOC] Call for Mentors

I can help co-mentor if nobody else has already signed up. > On Feb 14, 2022, at 7:46 AM, Joseph Lynch wrote: > > Hi Paulo! > > Thanks for organizing this. I would like to propose CASSANDRA-17381 > [1] which will implement/verify BoundedReadCompactionStrategy for this > year's GSOC and I can me

Re: GSOD 2022

I haven't looked into GSoD this year. However, the scope of a GSoD project has to be sufficient for the amount of time that is allocated by GSoD. They had 2 project lengths when we last participated - short & long. Projects need to be defined accordingly. It is a lot of work and I personally don

Re: GSOD 2022

ocess including payments. This has come up in a separate discussion on comdev so we'll see how it goes. As GSoD deadline is March 25, I am not sure if we can participate. > On Mar 8, 2022, at 5:13 PM, Dinesh Joshi wrote: > > I haven't looked into GSoD this year. However, the

Re: Updating our Code Contribution/Style Guide

I am also in favor of updating the style guide. We should ideally have custom checkstyle configuration that can ensure adherence to the style guide. I also don't think this is a contended topic. We want to explicitly codify our current practices so new contributors have an easier time writing co

Re: Updating our Code Contribution/Style Guide

into a linter. Plenty of the rules are stated in > a flexible manner, so as to permit breaches where overall legibility and > aesthetics are improved. > > > From: Dinesh Joshi > Date: Monday, 14 March 2022 at 23:44 > To: dev@cassandra.apache.org > Subject: Re: Updating

Re: [Discuss] replacement of airlift/airline framework in CLI tools

airline/airlift is deprecated. I suspect if there were any security issues they would not be fixed. Their project recommends moving to Airline 2 or picocli. I share Stefan's concern about the stability of the CLI and output formatting. We should avoid any breakages resulting from this migration.

Re: Welcome Aleksandr Sorokoumov as Cassandra committer

Congratulations Aleksandr! > On Mar 17, 2022, at 3:49 AM, Brandon Williams wrote: > > Congratulations and thank you Aleksandr! > > Kind Regards, > Brandon > > On Wed, Mar 16, 2022 at 8:15 AM Benjamin Lerer wrote: >> >> The PMC members are pleased to announce that Aleksandr Sorokoumov has >>

Re: [VOTE] Release dtest-api 0.0.13

+1 > On Mar 31, 2022, at 10:04 AM, David Capwell wrote: > > +1 > >> On Mar 31, 2022, at 9:53 AM, Alex Petrov wrote: >> >> Proposing the test build of in-jvm dtest API 0.0.13 for release. >> >> Repository: >> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=re

Re: Performance Engineering Track at ApacheCon NA?

That’s great to hear. I would also be available to help review submissions. > On Apr 6, 2022, at 8:14 AM, Sharan Foga wrote: > > Hi Paulo > > We have great news - the Performance Engineering track has been accepted so > we will be looking to encourage and promote CFP submissions for it. We a

Re: Apache Cassandra Marketing Meeting

This sounds great. Thanks for taking time to do this! Please post back notes of the meeting on the dev list so those who couldn't attend are in the loop. > On Apr 29, 2022, at 3:16 PM, Patrick McFadin wrote: > > Hi everyone, > > There are several community members working on various marketing

Re: [DISCUSS] Change code style guide WRT to @Override in subclasses / interface implementations

So your proposal is to always add override annotation? Or are there situations where you don’t want to add them? > > On Jun 3, 2022, at 6:53 AM, Alex Petrov wrote: > >  > Hi everyone, > > In our style guide [1], we have a following statement: > > > Avoid redundant @Override annotations when

Re: [DISCUSS] Change code style guide WRT to @Override in subclasses / interface implementations

thinking matches what David has mentioned: > > https://issues.apache.org/jira/browse/CASSANDRA-16096 > https://lists.apache.org/thread/mkskwxn921t5bkfmnog032qvnyjk82t7 > > I'll make sure to update the style guide itself, too, since it looks like > there was a vote, and int

Re: [DISCUSS] Change code style guide WRT to @Override in subclasses / interface implementations

ut of the woodwork. > > Perhaps I will just publish, and we can start addressing these queries in a > follow-up process. > > From: Dinesh Joshi > Date: Friday, 3 June 2022 at 16:57 > To: dev@cassandra.apache.org > Subject: Re: [DISCUSS] Change code style guide WRT

Re: [DISCUSS] Change code style guide WRT to @Override in subclasses / interface implementations

s. If anyone wants to escalate to a formal vote, feel free to > say so. > > I’ll update the wiki in a couple of days; we can always roll back if a > dissenting voice appears. > > > From: Dinesh Joshi > Date: Friday, 3 June 2022 at 18:34 > To: dev@cassandra.apa

Re: Cassandra project biweekly status update 2022-06-14

Better yet strive to maintain backward compatibility. There are very very few occasions where backward compatibility breakage is warranted. > On Jun 15, 2022, at 10:59 AM, bened...@apache.org wrote: > >  > > I agree a broader consensus beyond those on the jira ticket should be > > sought befo

Re: Thanks to Nate for his service as PMC Chair

Thank you Nate for your service! Welcome Mick! > > On Jul 11, 2022, at 5:54 AM, Paulo Motta wrote: > >  > Hi, > > I wanted to announce on behalf of the Apache Cassandra Project Management > Committee (PMC) that Nate McCall (zznate) has stepped down from the PMC chair > role. Thank you Nat

<    1   2   3   4   >