Re: Call for Volunteers: Community Over Code North America 2024

oops, actually meant by tomorrow eod anywhere (Fri, Aug/30). 😄 Cheers, Paulo On Thu, 29 Aug 2024 at 20:06 Paulo Motta wrote: > Friendly reminder: please submit your proposal by tomorrow (08/29) end of > day if you are planning to attend and would like to contribute to an > Apache

Re: Call for Volunteers: Community Over Code North America 2024

Feel free to reach out to me or #cassandra-comdev on ASF slack[2] if you have any suggestions or ideas. Cheers, Paulo [1] - https://www.apachecon.com/acna19/bof.html [2] - https://the-asf.slack.com/ On Wed, Aug 21, 2024 at 10:46 AM Paulo Motta wrote: > Hi, > > I would like to invite

Call for Volunteers: Community Over Code North America 2024

Hi, I would like to invite Cassandra contributors and enthusiasts to gather in Denver, USA from October 7 to 10 for the ASF conference Community Over Code (formerly known as ApacheCon). There will be two days of Cassandra talks on Monday (10/07) and Tuesday (10/08). You can check the event schedu

Re: Welcome Joey Lynch as Cassandra PMC member

Congratulations Joey! On Thu, 25 Jul 2024 at 00:55 Venkata Hari Krishna Nukala < n.v.harikrishna.apa...@gmail.com> wrote: > Congratulations Joey!! > > On Thu, 25 Jul 2024 at 7:20 AM, Joseph Lynch > wrote: > >> Thank you all for the warm wishes and I greatly appreciate this >> opportunity! >> >>

Re: Cassandra PMC Chair Rotation, 2024 Edition

Thank you Josh and congratulations Dinesh! On Thu, 20 Jun 2024 at 11:52 Josh McKenzie wrote: > Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra > Project Management Committee (PMC) I would like to welcome and congratulate > our next PMC Chair Dinesh Joshi (djoshi). > > Di

Re: [VOTE] CEP-24 Password validation / generation

+1 On Mon, Jun 17, 2024 at 5:32 AM Štefan Miklošovič wrote: > Hi everyone, > > I would like to start the voting for CEP-24 as all feedback in the > discussion threads seem to be addressed. > > Proposal: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=228494146 > JIRA under whi

Re: [DISCUSS] ccm as a subproject

As much as I'd like to remove the dependency on ccm I think we'll stick with it for a bit, so +1 on moving under the project umbrella. In the long term it would be nice to modernize integration test suites to use containers instead of processes for more flexibility and fewer dependencies for local

Re: Welcome Alexandre Dutra, Andrew Tolbert, Bret McGuire, Olivier Michallat as Cassandra Committers

Congratulations Alexandre, Andy, Bret and Olivier! :-) On Wed, Apr 17, 2024 at 1:11 PM Benjamin Lerer wrote: > The Apache Cassandra PMC is pleased to announce that Alexandre Dutra, > Andrew Tolbert, Bret McGuire and Olivier Michallat have accepted the > invitation to become committers on the jav

Re: [DISCUSS] CEP-40: Data Transfer Using Cassandra Sidecar for Live Migrating Instances

I am sympathetic to having a native fast instance migration solution as this is a common operational recipe. > It's valuable for Cassandra to have an ecosystem-native mechanism of migrating data between physical/virtual instances outside the standard streaming path. As Hari mentions, the current

Re: Update: C/C NA Call for Presentations Deadline Extended to April 15th

19 PM Paulo Motta wrote: > Hi, > > I wanted to update that the Call for Presentations deadline was extended > by two weeks to April 15th, 2024 for Community Over Code North America > 2024. Find more information on this blog post: > https://news.apache.org/foundation/entry/apa

Update: C/C NA Call for Presentations Deadline Extended to April 15th

Hi, I wanted to update that the Call for Presentations deadline was extended by two weeks to April 15th, 2024 for Community Over Code North America 2024. Find more information on this blog post: https://news.apache.org/foundation/entry/apache-software-foundation-opens-cfp-for-community-over-code-n

Two weeks remaining to submit abstracts to Community Over Code 2024

Hi, I'd like to send a friendly reminder that the deadline for submissions to Community Over Code North America 2024 ends in two weeks on April 1st, 2024. This conference will be held in Denver, Colorado, October 7-10, 2024. We're looking for abstracts in the following areas: * Customizing and t

Call for Presentations: Cassandra @ Community Over Code North America 2024

Hi, After a successful experience in ApacheCon 2022, the Cassandra track is back to Community Over Code North America 2024 to be held in Denver, Colorado, October 7-10, 2024. I will be facilitating this track and I would like to request abstract drafts in the following topics to be presented in t

Re: [Discuss] Repair inside C*

ss as TCM/Accord primitives become available and mature. On Thu, Feb 22, 2024 at 1:44 PM Paulo Motta wrote: > +1 to Josh's points, The project has considered native repair scheduling > for a long time but it was never made a reality due to the complex > considerations involved and ava

Re: [Discuss] Repair inside C*

+1 to Josh's points, The project has considered native repair scheduling for a long time but it was never made a reality due to the complex considerations involved and availability of custom implementations/tools like cassandra-reaper, which is a popular way of scheduling repairs in Cassandra. Un

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

vnodes/no-vnodes, offheap/onheap, and nothing about >> other stuff. To me running no-vnodes makes no sense because no-vnodes is >> just a special case of vnodes=1. On the other hand offheap/onheap buffers >> could be tested in unit tests. In short, I'd run dtests only with t

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

> It's also been questioned about why we don't just enable settings we recommend. These are settings we recommend for new clusters. *Our existing cassandra.yaml needs to be tailored for existing clusters being upgraded, where we are very conservative about changing defaults.* I think this unnece

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

> Perhaps it is also a good opportunity to distinguish subsets of tests which make sense to run with a configuration matrix. Agree. I think we should define a “standard/golden” configuration for each branch and minimally require precommit tests for that configuration. Assignees and reviewers can d

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

> If there’s an “old compatible default” and “latest recommended settings”, when does the value in “old compatible default” get updated? Never? How about replacing cassandra.yaml with cassandra_latest.yaml on trunk when cutting cassandra-6.0 branch? Any new default changes on trunk go to cassandra

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

I share Jacek’s and Stefan’s sentiment about the low value of requiring precommit j11+j17 tests for all changes. Perhaps this was needed during j17 stabilization but is no longer required? Please correct if I’m missing some context. To have a practical proposal to address this, how about: 1) Def

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

Cool stuff! This will make it easier to advance configuration defaults without affecting stable configuration. Wording looks good to me. +1 to include a NEWS.txt note. I'm ok with breaking trunk CI temporarily as long as failures are tracked and triaged/addressed before the next release. I haven'

Re: [VOTE] Release Apache Cassandra 4.1.4

+1 Reviewed changelog + tested docker image build (verify binary gpg+sha512sum) + jre11 startup. On Tue, Feb 6, 2024 at 4:03 PM Brandon Williams wrote: > I think we lost track of this one over some concern about > CASSANDRA-19097, but that turned out to be a test problem. +1 > > Kind Regards,

Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available

Thanks for the links. Checked the latest ci-cassandra 4.1 runs [1][2][3] and looks like the only consistently flaky across these runs is MemtableSizeTest being tracked on CASSANDRA-17298 so I think we're good to go. [1] https://ci-cassandra.apache.org/job/Cassandra-4.1/461/ [2] https://ci-cassandr

Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available

Is there a CI test run of this release candidate tag available ? Fwiw, docker image build (verify binary gpg+sha512sum) + jre11 startup looks good with: CASSANDRA_VERSION=4.1.4;docker build -t apache/cassandra-test:$CASSANDRA_VERSION --build-arg CASSANDRA_VERSION=$CASSANDRA_VERSION --build-arg C

Fwd: [Important] GSoC 2024 Project Ideas

See details below for submitting project ideas for GSoC 2024. This is a good opportunity to attract/mentor new contributors. I am not planning to mentor a project this year but would be happy to offer support if someone wants to submit a proposal. Please message me if you are interested or have an

Re: [VOTE] Release Apache Cassandra 4.0.12

DRA_SHA512=65de9cc32f3d22d55f5c7c3b1417285a41aabb70fa8a4ae8d9d85a58e644f43151bf4f386cc45773b6ac317db38c4576b139ca6b6fcdbbd16993d09ee2a5c2b8 https://github.com/pauloricardomg/docker-cassandra.git#:4.0 $ sudo docker run apache/cassandra-test:4.0.12 -f On Mon, Jan 22, 2024 at 11:08 PM Paulo Motta wrote: > +1 > > Tested docker image bui

Re: [VOTE] Release Apache Cassandra 4.0.12

+1 Tested docker image build (binary+checksum+signature) and container startup with: $ docker build --build-arg CASSANDRA_VERSION=4.0.12 --build-arg CASSANDRA_SHA512=65de9cc32f3d22d55f5c7c3b1417285a41aabb70fa8a4ae8d9d85a58e644f43151bf4f386cc45773b6ac317db38c4576b139ca6b6fcdbbd16993d09ee2a5c2b8 ht

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congratulations Maxim! On Tue, Jan 9, 2024 at 10:16 AM Benjamin Lerer wrote: > I am always late to the party. ;-) > Congrats Maxim! > > Le mar. 9 janv. 2024 à 13:16, Maxim Muzafarov a > écrit : > >> Thank you all so much, I'm happy to be part of such an active >> community and to be able to co

Call for Presentations closing soon: Community over Code EU 2024

I wanted to remind that the call for speakers for Community Over Code EU 2024 (formerly Apachecon EU) will be closing this Friday 2024/01/12 23:59:59 GMT. If you reside in Europe/EMEA and have an interesting talk proposal about using, deploying or modifying Apache Cassandra please see details belo

Re: Future direction for the row cache and OHC implementation

I like Dinesh's middle ground proposal, since this feature has valid uses. I'm not familiar with the row caching module, but would it make sense to take this opportunity to expose this feature as an optional Row Caching Module, disabled by default with an optional on-heap Caffeine implementation?

Fwd: Reminder: CFP for Community Over Code Europe is now open

There will be a Cassandra track at Community Over Code Europe 2024 (formerly known as Apachecon EU) that will happen on Bratislava, Slovakia on 3 Jun 2024. If you have any talks proposals about using, deploying or modifying Apache Cassandra please make a submission before 12 Jan 2024 to speak at a

Re: [VOTE] Release Apache Cassandra 5.0-beta1

y a PMC via binding -1 Opinions supporting the proposal are also valuable, provided there are no valid claims against a proposal. On Wed, 29 Nov 2023 at 22:27 Paulo Motta wrote: > To me, the goal of a beta is to find unknown bugs. If no new bugs are > found during a beta release, then

Re: [VOTE] Release Apache Cassandra 5.0-beta1

To me, the goal of a beta is to find unknown bugs. If no new bugs are found during a beta release, then it can be automatically promoted to RC via re-tagging. Likewise, if no new bugs are found during a RC after X time, then it can be promoted to final. If we end up not releasing a final 5.0 artif

Re: [DISCUSS] Update default disk_access_mode to mmap_index_only on 5.0

change in 5.0? If not, we will merge in 24 hours. Thanks, Paulo [1] - https://lists.apache.org/thread/w0gkdj7fhylycqwmd73p0kfck7jr8qth [2] - https://issues.apache.org/jira/browse/CASSANDRA-19021 On Wed, Sep 6, 2023 at 5:12 PM Paulo Motta wrote: > > I wonder why disk_access_mode property is

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Nice, thanks for the quick fix! Checked and working now. On Sat, 4 Nov 2023 at 21:11 Mick Semb Wever wrote: > > > On Sun, 5 Nov 2023 at 00:49, Paulo Motta wrote: > >> > With the publication of this release I would like to switch the >> default 'latest'

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

> With the publication of this release I would like to switch the default 'latest' docs on the website from 4.1 to 5.0. Are there any objections to this ? It looks like the switch of latest to 5.0 broken some top search links (returns 404 to me): [1] - https://www.google.com/search?q=apache+cas

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

urse. Also, we need a bit >> more investigation here. I can try to take a look tomorrow in more >> detail if no one beats me to that. >> >> Best regards, >> Ekaterina >> >> >> On Fri, 3 Nov 2023 at 20:01, Paulo Motta wrote: >> >

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Clarification: - When running nodetool only the "Unknown module" warnings show up. All warnings show up during startup. On Fri, Nov 3, 2023 at 7:58 PM Paulo Motta wrote: > Launched a tarball-based 5.0-alpha2 container on top of > "eclipse-temurin:17-jre-focal" and the

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Launched a tarball-based 5.0-alpha2 container on top of "eclipse-temurin:17-jre-focal" and the server starts up fine, can run nodetool and cqlsh. I got these seemingly harmless JDK17 warnings during startup and when running nodetool (no warnings on JDK11): WARNING: Unknown module: jdk.attach spec

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

Even if it was not formally prescribed as far as I understand, we have been following the "only merge on Green CI" custom as much as possible for the past several years. Is the proposal to relax this rule for 5.0? On Tue, Oct 31, 2023 at 1:02 PM Jeremiah Jordan wrote: > You are free to argue val

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

> Sure, some like big shiny new numbers for new features and new APIs. But if we follow the online upgrade-compatibility approach, clusters will be able to upgrade from any 4.x to 5.1, therefore from the operators PoV the "6" is not required. > Aside from my desire to make our semver consistent to

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

>From a user perspective I have to say I was excited to see Accord/TCM being released on 5.0 but at the same time a little nervous about seeing so many overhauling features being shipped on the same release. I think rushing last minute features hurts the stability goals we set for the project. As

Re: [DISCUSS] Update default disk_access_mode to mmap_index_only on 5.0

;> >> I don’t have numbers handy to share, but my experience has been >> significantly lower read latency and I wouldn’t run with auto. I’ve also >> not observed substantial heap pressure after switching - it was strictly an >> improvement. >> >> - Scott >> >>

[DISCUSS] Update default disk_access_mode to mmap_index_only on 5.0

Hi, I've been bitten by OOMs with disk_access_mode:auto/mmap that were fixed by changing to disk_access_mode:mmap_index_only. In a particular benchmark I got 5x more read throughput on 3.11.x with disk_access_mode: mmap_index_only vs disk_access_mode: auto/mmap. Changing disk_access_mode to mmap_

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 On Tue, Jun 13, 2023 at 10:16 AM Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > On Tue, Jun 13, 2023 at 9:15 AM Jeremy Hanna > wrote: > > > > Calling for a vote on CEP-8 [1]. > > > > To clarify the intent, as Benjamin said in the discussion thread [2], > the goal of this vote i

Re: Welcome our next PMC Chair Josh McKenzie

Thanks Mick and congratulations Josh!! :) On Thu, Mar 23, 2023 at 5:33 PM Erick Ramirez wrote: > Thanks Mick for everything you've done and continue to do for the project! > Congratulations Josh and thanks for stepping up! The community is in good > shape! 🍻 >

Re: [EXTERNAL] Re: [DISCUSS] Next release date

> I would like to propose a partial freeze of 5.0 in June. Would that be a trunk freeze, or freeze of a cassandra-5.0 branch? I agree with a branch freeze, but not with trunk freeze. I might work on small features after June and would be happy to delay releasing these on 5.0+, but delaying merge

[CASSANDRA-18102] Add a virtual table to list snapshots

Hi, I wanted to give a heads up that we're adding a new virtual table on CASSANDRA-18102[1] to query snapshots. This is similar to the nodetool listsnapshots command but give more flexibility to users by allowing querying snapshots by keyspace/size/creation date, for example: ### cqlsh> SELECT *

Re: Degradation of availability when using NTS and RF > number of racks

feedback. >> >> >> >> I think that emitting a warning upon keyspace creation (and >> alteration) should be enough for starters. If somebody can not live without >> 100% bullet proof solution over time we might choose some approach from the >> offered ones. As

Re: [DISCUSS] Should separate snapshots with the same name be allowed in different tables?

e/StorageService.java#L4317 > > > From: Paulo Motta > Sent: Monday, March 6, 2023 5:59 > To: Cassandra DEV > Subject: [DISCUSS] Should separate snapshots with the same name be allowed > in different tables? > > NetApp Security WARNIN

Re: Degradation of availability when using NTS and RF > number of racks

It's a bit unfortunate that NTS does not maintain the ability to lose a rack without loss of quorum for RF > #racks > 2, since this can be easily achieved by evenly placing replicas across all racks. Since RackAwareTopologyStrategy is a superset of NetworkTopologyStrategy, can't we just use the ne

[DISCUSS] Should separate snapshots with the same name be allowed in different tables?

Hi, It's possible to create a snapshot on a set of tables with the same name name/tag with: $ nodetool snapshot --kt-list ks.tb,system.local -t mysnapshot $ nodetool listsnapshots [..] mysnapshot system local 1.16 KiB 21.47 KiB2023-03-02T13:19:13.757Z mysnapshot ks tb 1.02 KiB

Re: Welcome Patrick McFadin as Cassandra Committer

Congratulations for this well deserved recognition, Patrick! Thank you for all the energy you inject into this community! :-) On Sun, Feb 5, 2023 at 7:17 PM Patrick McFadin wrote: > Thank you everyone for all the well wishes here and in other parts of the > interwebs. It's always a privilege to

Re: Should we change 4.1 to G1 and offheap_objects ?

I tend to agree with Aleksey's sentiment. Why do we need to change the default in a minor release if we already provide G1 options for users that want to opt-in? On Thu, Jan 12, 2023 at 9:46 AM Aleksey Yeshchenko wrote: > Switching a major default in a minor release is way worse than doing it in

Re: Weird results

I recently came across this issue. I was able to fix it with "ant realclean" + "ant build", indicating it's probably a leftover configuration from a previous test. We probably need to find which tests with a non default partitioner are not being properly cleaned up. Em qui., 15 de dez. de 2022 às

Re: [DISCUSS] API modifications and when to raise a thread on the dev ML

It feels bit of overkill to me to require addition of any new virtual tables/JMX/configuration/knob to go through a discuss thread. If this would require 70 threads for the previous release I think this would easily become spammy and counter-productive. I think the burden should be on the maintain

[PROPOSAL] Add docker-based "Hello World" tutorial in-tree for new developers

Hi everyone, For the Grace Hopper Open Source Day mentoring hackathon [1] on Sept. 16 I created a short guide to handout to participants interested in contributing to Cassandra so they could get quickly get started working on LHF tickets. There were about 5 participants and most of them were able

Re: Looking for documentation tasks to work on

Welcome Sharan! :) One of the features that is going to be released in 4.1 is the ability to add TTL to snapshots, but this hasn't been documented yet afaik. There's a preliminary documentation patch available on https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take a stab at

Invitation to take the 2022 ASF Community Survey

Hello everyone, The 2022 ASF Community Survey is looking to gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We want to find areas where we can continue to do great work, and others whe

Re: Cassandra project status update 2022-08-17

Please disconsider previous message, I missed Ekaterina's message :) Em qua., 17 de ago. de 2022 às 17:35, Paulo Motta escreveu: > > testAutoSnapshotTTIOnDropAfterRestart has failed a few times so there's > some legit flake there: > https://ci-cassandra.apache.org

Re: Cassandra project status update 2022-08-17

> testAutoSnapshotTTIOnDropAfterRestart has failed a few times so there's some legit flake there: https://ci-cassandra.apache.org/job/Cassandra-4.1/138/testReport/org.apache.cassandra.distributed.test/AutoSnapshotTtlTest/testAutoSnapshotTTlOnDropAfterRestart_2/. No build lead lately so we don't hav

Re: [DISCUSS] Remove Dead Pull Requests

I recently came across a github automation in the docker project that I found interesting: https://github.com/docker/for-win/issues/7905#issuecomment-787212626 "Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed

Thanks to Nate for his service as PMC Chair

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 Nate for all the work you did as the PMC chair! The Apache Cassandra PMC has nominated Mick Semb Wever (mck) as the new PMC c

Re: Adding RSS feed to the Apache Cassandra website.

Nice initiative! All options look good to me in this preference order: 2, 1, 3. Em seg., 30 de mai. de 2022 às 06:34, Benjamin Lerer escreveu: > Hi everybody, > > Chris has been looking with the web design team about adding an RSS feed > to our website. Unfortunately there are some complications

Re: Performance Engineering Track at ApacheCon NA?

gt; Thanks for the feedback. If we do get the track accepted then we will > definitely be needing help reviewing the submissions - so may take you up > on your offer :-) > > > > Thanks > > Sharan > > > > On 2022/03/14 16:32:23 Paulo Motta wrote: > > > Thi

Re: Code freeze starts 1st May. Anything to be addressed?

r to set to > identify the host in some way for them, and another one for internal usage, > but I’m not sure that’s a great idea. > > > > *From: *Paulo Motta > *Date: *Wednesday, 27 April 2022 at 18:20 > *To: *Cassandra DEV > *Subject: *Re: Code freeze starts 1st May. A

Re: Code freeze starts 1st May. Anything to be addressed?

ly make use of the feature, its very > existence would constrain what we can assume/assert about host ids going > forward. Given that drawback, the fact that this is a very niche feature > makes it even less compelling. > > > On 27 Apr 2022, at 18:20, Paulo Motta wrote: > > Ful

Re: Code freeze starts 1st May. Anything to be addressed?

to control their node UUIDs for inventory purposes, so this seems like a valid use case for this feature. Em qua., 27 de abr. de 2022 às 14:20, Paulo Motta escreveu: > Fully agree we should add a collision check but I don't understand why > this optional feature is bad/dangerous afte

Re: Code freeze starts 1st May. Anything to be addressed?

Fully agree we should add a collision check but I don't understand why this optional feature is bad/dangerous after we add this ability? Can you provide an example of a potential issue? I don't expect this property to be used by most users, except power users which normally know what they're doing

Re: Code freeze starts 1st May. Anything to be addressed?

Hi Ekaterina, Thanks for bringing this up. I'm hoping to complete the following tickets before the freeze before May 1st: - List snapshots of dropped tables which will unblock: - Add a

Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

I was unpleasantly surprised to find out that Linkedin group posts are not visible outside of the group, which greatly reduces post visibility. I originally supported the group creation because I thought the posts would be visible outside the group but this doesn't seem to be the case. The only th

Re: [DISCUSS] Should we deprecate / freeze python dtests

Re: [DISCUSS] Should we deprecate / freeze python dtests > > > In fact there is a high learning curve to setup cassandra-dtest > environment > > I think this is fairly well documented: > https://github.com/apache/cassandra-dtest/blob/trunk/README.md > > On Tue, Mar 29, 2022 at 5:27

Re: [DISCUSS] Should we deprecate / freeze python dtests

tests (the >> withConfig logic is a bit cryptic), so don’t think the docs would be too >> much work >> >> >> On Mar 29, 2022, at 5:48 AM, Josh McKenzie wrote: >> >> we should at least write extensive documentation on how to use/modify >> in-jvm

Re: [DISCUSS] Should we deprecate / freeze python dtests

uch lower for pyhton dtests. So we should at least write extensive documentation on how to use/modify in-jvm dtest framework before deprecating python dtests. Em ter., 29 de mar. de 2022 às 06:58, Paulo Motta escreveu: > > They use a separate implementation of instance initialization and

Re: [DISCUSS] Should we deprecate / freeze python dtests

> They use a separate implementation of instance initialization and thus they test the test server rather than the real node. I also have this concern. When adding a new service on CASSANDRA-16789 we had to explicitly modify the in-jvm dtest server to match the behavior from the actual server [1]

Re: Welcome Aleksandr Sorokoumov as Cassandra committer

Congratulations Alex, well deserved! :-) Em qua., 16 de mar. de 2022 às 10:15, Benjamin Lerer escreveu: > The PMC members are pleased to announce that Aleksandr Sorokoumov has > accepted > the invitation to become committer. > > Thanks a lot, Aleksandr , for everything you have done for the proj

Re: Using labels on pull requests in GitHub

Thanks for doing this Stefan. The fact that PRs are abandoned and piling up on github demonstrates a hygiene problem and creates a bad user experience to newcomers which are accustomed to the Github workflow. I'm supportive of any initiative to improve this I think starting labelling PRs manually

Re: Performance Engineering Track at ApacheCon NA?

This Apachecon track sounds fun! I hope someone from the Cassandra community steps up to help on this track. I would be happy to help on reviews but not organize the event per se as I will likely not attend the event. Em sex., 11 de mar. de 2022 às 09:26, sharanf escreveu: > Hi All > > The call

Re: GSOD 2022

Any of the docs contributors interested in taking the lead on this? Perhaps Dinesh could share some tips on how to create the GSoD application. I think there is a lot of documentation that needs to be created/migrated, would be nice to have some external help on this. For instance, some virtual t

Re: [DISCUSS] Next release cut

Thanks for bringing this topic for discussion Benjamin. > The cassandra-4.0 branch was created on the 1st of May last year. So it would make sense to do something similar this year. Does it sound reasonable? +1 to having a predictable release date and May 1st sounds good to me. > Should we plan

Re: [GSOC] Call for Mentors

any further context I need > to provide or jira tagging I need to do (I labeled it gsoc and > gsoc2022). > > [1] https://issues.apache.org/jira/browse/CASSANDRA-17381 > > -Joey > > > On Fri, Feb 11, 2022 at 1:54 PM Paulo Motta > wrote: > > > > Unfortunately

Re: [DISCUSS] CASSANDRA-17292 Move cassandra.yaml toward a nested structure around major database concepts

I think we can easily support a hybrid world where we can support legacy configuration safely while allowing new clusters from leveraging modern configuration. And eventually "switch" to only support the new configuration layout. > If we make "a big cut" and old way of doing things would not be po

Re: [FOR REVIEW] Content Pipeline Process wiki

Fixing the updated link: https://cwiki.apache.org/confluence/display/CASSANDRA/%28draft%29+Apache+Cassandra+blog+content+process (haven't reviewed yet) Em qui., 17 de fev. de 2022 às 10:21, Chris Thornett escreveu: > For those who are interested in content, I've added a draft page on the > Apac

Re: Welcome Anthony Grasso, Erick Ramirez and Lorina Poland as Cassandra committers

Nice work guys! Very happy to see non-core-database contributors being recognized by the project as committers. Em ter., 15 de fev. de 2022 às 16:28, Melissa Logan escreveu: > Spectacular -- congrats, all! > > On Tue, Feb 15, 2022 at 11:27 AM Chris Thornett > wrote: > >> Fantastic news! Congrat

Re: [GSOC] Call for Mentors

%20Done%20 > > It looks like we ended up with no gsoc projects submitted? Or am I > querying wrong? > > henrik > > On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta > wrote: > >> Hi Henrik, >> >> I am happy to give feedback to project ideas - but they ultimatel

Dynamic Table TTL

Hi, Just a heads up that I created CASSANDRA-17372 to explore supporting dynamic table TTL and would like to hear your feedback (on the idea) before moving forward with a design. Please add any potential comments to the ticket. Cheers, Paulo [1] - https://issues.apache.org/jira/browse/CASSANDRA

Re: Build tool

> I am productive today with ant. I will almost certainly take a productivity hit sometime during and after the migration to maven, as will others. I took a massive productivity hit when In-JVM dtests landed the codebase, but this was not a consideration when that framework was added because it wa

Re: [GSOC] Call for Mentors

already pinged you on Slack about their ideas. > When you say we don't have any subscribed ideas, what is missing? > > henrik > > On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta > wrote: > >> Hi everyone, >> >> We need to tell ASF how many slots we will need for

Re: [GSOC] Call for Mentors

se do so by no later than February 10 to allow sufficient time for follow-ups. Cheers, Paulo Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta escreveu: > Hi everyone, > > Following up from the initial GSoC Kick-off thread [1] I would like to > invite contributors to submit GSoC

[GSOC] Call for Mentors

Hi everyone, Following up from the initial GSoC Kick-off thread [1] I would like to invite contributors to submit GSoC project ideas. In order to submit a project idea, just tag a JIRA ticket with the "gsoc" label and add yourself to the "Mentor" field to indicate you're willing to mentor this pro

Re: UDF future

This proposal looks good to me, +1. I was wondering if we should not run this proposal on the user@ list to check if there's any additional feedback in addition to the informal Twitter and Linkedin channels? Em qua., 19 de jan. de 2022 às 10:18, Sylwester Lachiewicz < slachiew...@gmail.com> escrev

Re: Google Summer of Code 2022 - Kick-off

few people to figure out how we > could prioritize this during January. > > henrik > > On Fri, Jan 14, 2022 at 2:52 PM Paulo Motta > wrote: > >> Hi everyone, >> >> I'd like to follow-up on this as GSoC timeline starts soon in February >> [1]. &

Re: Google Summer of Code 2022 - Kick-off

ns on how to triage tickets on JIRA and propose project ideas in the mailing list, and a twitter campaign pointing to the blog post. What do you think? Paulo [1] - https://developers.google.com/open-source/gsoc/timeline Em sex., 12 de nov. de 2021 às 11:30, Paulo Motta escreveu: > We

Re: [DISCUSS] Periodic snapshot publishing with minor version bumps

I dislike the idea of using minors to represent snapshot releases because I think skipping final release numbers can confuse the vast majority of non-power users which do not use snapshot releases. I like the idea of using pre-release tags (ie. alpha1, alpha2, or PRE1, PRE2, etc) for snapshot rele

Re: [DISCUSS] Next release cut

+1 to cut 4.1 in May. It would be great to attain the yearly cut cadence if possible. Em ter., 14 de dez. de 2021 às 09:45, Mick Semb Wever escreveu: > > We cut 4.0 in May and released it in July. It is difficult to plan for a > release date so we should probably agree on the cut date. One year

Re: [DISCUSS] Proposal for a December event

rent people might be interested in different levels > of difficulties. > > Le mer. 24 nov. 2021 à 18:46, Paulo Motta a > écrit : > > > The idea sounds great to me in principle - the only issue I see is: > > > > > we promote a simple ticket everyday for a new

Re: [DISCUSS] Proposal for a December event

The idea sounds great to me in principle - the only issue I see is: > we promote a simple ticket everyday for a newcomer to pickup During GSoC this year I had difficulty selecting "simple tickets for newcomers to pickup" for the following reasons: - inconsistency in LHF tagging (not many of the e

Re: [DISCUSS] Mentoring newcomers

Count me in. Em sex., 12 de nov. de 2021 às 14:16, Brandon Williams escreveu: > I'm interested. > > On Fri, Nov 12, 2021 at 11:05 AM Benjamin Lerer wrote: > > > > Hi everybody > > > > As discussed in the *Creating a new slack channel for newcomers* thead, a > > solution to help newcomers engage

Re: Google Summer of Code 2022 - Kick-off

; > On 12/11/21 10:02, Benjamin Lerer wrote: > > Thanks a lot Paulo for pushing that forward. That is a great way to grow > > our community. > > > > Le jeu. 11 nov. 2021 à 14:32, Paulo Motta a > > écrit : > > > >> Hi, > >> > >&g

Google Summer of Code 2022 - Kick-off

Hi, The Google Summer of Code organization announced some exciting changes to the program next year [1]: (1) Starting in 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. (2) GSoC Contributors will be able

  1   2   3   >