Re: [DISCUSS] Adding support for BETWEEN operator

This is a great feature addition to CQL! I get asked about it from time to time but then people figure out a workaround. It will be great to just have it available. And right on Simon! I think the only project I had as a high school senior was figuring out how many parties I could go to and still

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

I finally got a chance to digest this CEP and am happy to see it raised. This feature has been left to the end user for far too long. It might get roasted for scope creep, but here goes. Related and something that I've heard for years is the ability to migrate a single keyspace away from a set of

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

Congratulations, everyone. I am loving this new direction for the project! On Wed, Apr 17, 2024 at 11:16 AM Yifan Cai wrote: > Congrats all > -- > *From:* Josh McKenzie > *Sent:* Wednesday, April 17, 2024 11:05:29 AM > *To:* dev > *Subject:* Re: Welcome Alexandre

Re: Welcome Brad Schoening as Cassandra Committer

Yay! Congrats Brad! On Wed, Feb 21, 2024 at 2:06 PM Jeremy Hanna wrote: > Congratulations Brad! > > On Feb 21, 2024, at 3:59 PM, Leo Toff wrote: > > Congratulations Brad! Thank you for helping me onboard  > > On Wed, Feb 21, 2024 at 1:56 PM Jeremiah Jordan > wrote: > >> Congrats! >> >> On

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congratulations Maxim! Thank you for all you've done in the project and everything to come! Patrick On Mon, Jan 8, 2024 at 12:32 PM Miklosovic, Stefan via dev < dev@cassandra.apache.org> wrote: > Great news! Congratulations. > > > From: Josh McKenzie >

Re: Harry in-tree (Forked from "Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?")

It was great having some more extended discussions about Harry in person last week. Anything we can do to make it easier for anyone to test Cassandra thoroughly is an easy +1 from me! Thanks for all your efforts so far, Alex. Patrick On Fri, Dec 22, 2023 at 8:03 AM Jacek Lewandowski <

Can't make it to Cassandra Summit but want to see the talks?

Hi everyone, The Linux Foundation will be streaming all of the talks from the Cassandra Summit. Finding the streams is very easy. Go to the conference schedule: https://events.linuxfoundation.org/cassandra-summit/program/schedule/ Each talk has a YouTube link associated with it. The Keynotes

Re: Welcome Mike Adamson as Cassandra committer

Yay! Congratulations Mike. Well deserved! On Fri, Dec 8, 2023 at 7:00 AM Andrés de la Peña wrote: > Congrats Mike! > > On Fri, 8 Dec 2023 at 14:53, Jeremiah Jordan > wrote: > >> Congrats Mike! Thanks for all your work on SAI and Vector index. Well >> deserved! >> >> On Dec 8, 2023 at 8:52:07

Re: Introducing the Cassandra Catalyst program!

So excited for this program! It's been a long time coming but wow, what a great way to recognize individuals advocating for Cassandra in their own communities. Let's get out there and start nominating! Patrick On Fri, Dec 1, 2023 at 9:51 AM Melissa Logan wrote: > The Cassandra community is

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congratulations and welcome, Francisco! On Thu, Nov 30, 2023 at 2:45 AM Maxim Muzafarov wrote: > My congratulations, Francisco! :-) > > On Wed, 29 Nov 2023 at 13:30, Andrés de la Peña > wrote: > > > > Congrats Francisco! > > > > On Wed, 29 Nov 2023 at 11:37, Benjamin Lerer wrote: > >> > >>

Cassandra Summit: Engage those networks!

Hi everyone, We are a couple of weeks away from Cassandra Summit. People get busy and forget to register or miss that there is even a summit happening. Let's make sure everyone who wants to go gets a chance! - If you are going, get on the social media of your choice and let everyone know you'll

Re: [VOTE] Release Apache Cassandra 5.0-beta1

as another >> alpha and we do beta1 once the known fixes land? >> >> On Nov 28, 2023, at 12:21 PM, J. D. Jordan >> wrote: >> >>  >> -0 (NB) on this cut. Given the concerns expressed so far in the thread I >> would think we should re-cut beta1 at the end o

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect especially if there are declared known issues. We need people outside of this tight group using it and finding issues. I know how this rolls. Very few people touch a Alpha release. Beta is when the engine starts and we need to get

Cassandra Summit: Early registration discount ends tomorrow

Hi everyone, If you've registered for Cassandra Summit, then ignore this email. If not! Time to get moving. The deadline ends tomorrow. Link to register: https://events.linuxfoundation.org/cassandra-summit/register/ Discount code: 23CS20 (Yes you can use it with the early registration price)

Re: Time to register for the Cassandra Summit 2023!

/travel-funding/ I hope many of you will take advantage of this program and join us in San Jose! Patrick On Thu, Nov 9, 2023 at 7:15 AM Patrick McFadin wrote: > Hi everyone! > > I'm going to keep this short, but it's time to gather the Cassandra > community. December 12-13 in San Jos

Time to register for the Cassandra Summit 2023!

Hi everyone! I'm going to keep this short, but it's time to gather the Cassandra community. December 12-13 in San Jose. Earlybird registration pricing ends November 21 so don't delay. Registration page: https://events.linuxfoundation.org/cassandra-summit/register/ Use my discount code for 20%

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

elease why not take it as an opportunity to release > more things. I am not saying that we will. Just that we should let that > door open. > >>>> > >>>> > >>>> Agreed. This is the reason I brought up the possibility of not > branching off 5

Re: Project Status Update: 90-day catch-up edition [2023-10-27]

Sent you an invite Sam. Welcome to the community! On Fri, Oct 27, 2023 at 10:31 AM Sam wrote: > Please can I have an invite to the Slack workspace on this email. I'd like > to take a look through some of the items for first time contributors :-) > > Thanks! > > On Fri, 27 Oct 2023 at 18:10,

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

lease a 5.1-alpha1, > 5.1-dev-preview1, what ever we want to version this thing, from trunk or > any other branch name we want. > > -Jeremiah > > On Oct 24, 2023 at 2:03:41 PM, Patrick McFadin wrote: > > I would like to have something for developers to use ASAP to try the >

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

ding it back. If there's 2 big releases in 6 >> months the community isn't any worse off. >> >> We either ship something, or nothing, and something is probably better. >> >> Jon >> >> >> On 2023/10/24 16:27:04 Patrick McFadin wrote: >> >> +1 to w

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

+1 to what you are saying, Josh. Based on the last survey, yes, everyone was excited about Accord, but SAI and UCS were pretty high on the list. Benedict and I had a good conversation last night, and now I understand more essential details for this conversation. TCM is taking far more work than

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

I’m going to be clearer in my statement. This has to be in 5.0, even if it’s alpha and ships after December, or this is going to be disaster that will take us much longer to unravel. On Mon, Oct 23, 2023 at 7:49 AM Jeremiah Jordan wrote: > +1 from me assuming we have tickets and two committer

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

I'm really surprised to see this email. The last I heard everything was on track for getting into 5.0 and TBH and Accord is what a majority of users are expecting in 5.0. And how could this be a .1 release? What is it going to take to get it into 5.0? What is off track and how did we get here?

Cassandra Summit Update!

Hello Cassandra Community, Below you'll find the updated announcement being posted on the Cassandra website. The short version for short attention spans: - Cassandra Summit will be co-located with the AI.Dev conference. One ticket, two conferences. - CFP for an AI track for the Cassandra

Re: [Discuss] ​​CEP-35: Add PIP support for CQLSH

Dinesh raises some good points. If we do adopt this, there will be non-zero overhead of the release process. This is fine but we need volunteers to run this process. My understanding is that they need to be ideally PMC or at least Committers on the project to go through all the steps to

Raw results from User Survey

Thanks to everyone who participated in this survey. We had a significant enough responses to give this a legitimacy. 220 responses! I wanted to get the raw results out first so everyone can participate with the full picture. I'll work on a blog post to post on the Apache web site after this is

Who wants a free Cassandra t-shirt?

We have about another week left on the user survey I posted last week. The response has been slow, so it's time to get things in gear. I found a box of Cassandra t-shirts that will make an excellent thank you for anyone filling out the survey. Once the survey window closes, I'll pick a random

Apache Cassandra User Survey

It’s been a long time since I’ve asked the community for feedback in a poll or otherwise. A lot is changing in the data world, and we have an exciting Cassandra release coming up with v5! I would like to ask for five or ten minutes of your time to answer some questions about how you use Cassandra

[DISCUSS] Conducting a User Survey

For quite a few years, I have done Twitter polls to gather helpful information about how people use Apache Cassandra. Twitter is no longer the best place to conduct this kind of activity since it has become a ghost town. We should ask more comprehensive questions to get the pulse of our user

Re: CASSANDRA-18654 - start publishing CQLSH to PyPI as part of the release process

I would say it helps a lot of people. 45k downloads in just last month: https://pypistats.org/packages/cqlsh I feel like a CEP would be in order, along the lines of CEP-8: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+Datastax+Drivers+Donation Unless anyone objects, I can help

Re: [VOTE] CEP 33 - CIDR filtering authorizer

+1 On Wed, Jun 28, 2023 at 3:42 AM Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > > On Tue, Jun 27, 2023 at 12:17 PM Shailaja Koppu wrote: > > > > Hi Team, > > > > (Starting a new thread for VOTE instead of reusing the DISCUSS thread, > to follow usual procedure). > > > > Please

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 On Wed, Jun 14, 2023 at 2:39 PM Adam Holmberg wrote: > +1 > > (long time coming!) > > On Wed, Jun 14, 2023 at 3:51 AM Jorge Bay Gondra > wrote: > >> +1 nb >> >> On Wed, Jun 14, 2023 at 9:13 AM Sam Tunnicliffe wrote: >> >>> +1 >>> >>> On 13 Jun 2023, at 15:14, Jeremy Hanna >>> wrote: >>>

Re: [VOTE] CEP-30 ANN Vector Search

Andy, Good to see you on the ML again! CEP-30 is slated for release with 5.0 later in the year. Until then, you'll need to do a local build or try it out in a preview in Astra. A few of us have been talking about creating a preview docker image since there is some interest in having it run in

Re: [VOTE] CEP-30 ANN Vector Search

+1 Love the buzz this creating with new users. Thanks for the work on this Jonathan. On Thu, May 25, 2023 at 8:45 AM Jonathan Ellis wrote: > Let's make this official. > > CEP: >

Re: Vector search demo, and query syntax

| I first stumbled a bit with "there's no where clause and no filtering allowed…" | But I doubt that reaction from any experienced cql user will last more than a moment. I was also wondering about that, but this syntax looks good. More importantly, it will be easy to explain to end users.

Re: [DISCUSS] The future of CREATE INDEX

1 Yes 4 On Mon, May 15, 2023 at 3:00 AM Benedict wrote: > 3: CREATE INDEX (Otherwise 2) > No > If configurable, should be a distributed configuration. This is very > different to other local configurations, as the 2i selected has semantic > implications, not just performance (and the perf

Re: [DISCUSS] The future of CREATE INDEX

s happens is super visible in both NEWS and simultaneously updates the > to-string / to-cql representation of the schema in cqlsh / drivers / > snapshots > > On Wed, May 10, 2023 at 8:27 PM Patrick McFadin > wrote: > >> Having pulled a lot of developers out of the 2i fire, I

Re: [DISCUSS] The future of CREATE INDEX

Having pulled a lot of developers out of the 2i fire, I would love it if defaults got a bit more sane. Adding USING...WITH... on CREATE INDEX seems like the right move for most developers that don't read docs and assume behavior. As much as I hate that 2i would be the configured default, I get

Re: [VOTE] CEP-29 CQL NOT Operator

+1 On Tue, May 9, 2023 at 10:58 AM Caleb Rackliffe wrote: > +1 > > On Tue, May 9, 2023 at 12:04 PM Piotr Kołaczkowski > wrote: > >> Let's vote. >> >> >> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator >> >> Piotr Kołaczkowski >> e. pkola...@datastax.com >> w.

Re: CEP-30: Approximate Nearest Neighbor(ANN) Vector Search via Storage-Attached Indexes

Under the goals section, there is this line: 1. Scatter/gather across replicas, combining topK from each to get global topK. But what I'm hearing is, exactly how will that happen? Maybe this is an SAI question too. How is that verified in SAI? On Tue, May 9, 2023 at 11:07 AM David

Re: [POLL] Vector type for ML

DENSE VECTOR means I need to go read docs (and then probably > double-check in the source to be sure) to be sure what exactly is going on. > > Cheers, > > Derek > > On Fri, May 5, 2023 at 9:54 AM Patrick McFadin wrote: > >> I hope we are willing to consider develope

Re: [POLL] Vector type for ML

one vote as the list looked like a > summary, but you mentioned the first was your preference > > *Syntax* > > *Jonathan Ellis* > > *David Capwell* > > *Josh McKenzie* > > *Caleb Rackliffe* > > *Patrick McFadin* > > *Brandon Williams* > > *Mike Adamson*

Re: [POLL] Vector type for ML

y with us supporting: > * NON-NULL FROZEN > * DENSE_VECTOR as syntactic sugar for the above > > If getting into the "built-in syntactic sugar mapping for communities and > specific use-cases" is something we're willing to consider. > > On Fri, May 5, 2023, at 7:26 AM, Patri

Re: [POLL] Vector type for ML

;> If that isn't intuitive to anyone else, I don't really have a strong >>> opinion...but...conflating "frozen" and "dense" seems like a bad idea. One >>> should indicate single vs. multi-cell, and the other the presence or >>> absence of nulls/zeros

Re: [VOTE] CEP-28: Reading and Writing Cassandra Data with Spark Bulk Analytics

As somebody who gave this talk: https://youtu.be/9xf_IXNylhM I love the evolution of this topic. Excited to see this! ++1 nb Patrick On Thu, May 4, 2023 at 11:35 AM C. Scott Andreas wrote: > +1nb. > > As someone familiar with this work, it's pretty hard to overstate the > impact it has on

Re: [POLL] Vector type for ML

I agree with David's reasoning and the use of DENSE (and maybe eventually SPARSE). This is terminology well established in the data world, and it would lead to much easier adoption from users. VECTOR is close, but I can see having to create a lot of content around "How to use it and not get in

Re: [POLL] Vector type for ML

> >> On May 2, 2023, at 3:04 PM, Benedict wrote: >> >> But it’s so trivial it was already implemented by David in the span of >> ten minutes? If anything, we’re slowing progress down by refusing to do the >> extra types, as we’re busy arguing about it rather than del

Re: [POLL] Vector type for ML

t hey ho. > > On 2 May 2023, at 20:57, Patrick McFadin wrote: > >  > I'll speak up on that one. If you look at my ranked voting, that is where > my head is. I get accused of scope creep (a lot) and looking at the initial > proposal Jonathan put on the ML it was mostly "

Re: [POLL] Vector type for ML

type, not the ANN). > > I am surprised, and the blurbs accompanying votes so far don’t seem to > touch on this, mostly just endorsing the idea of a vector. > > > On 2 May 2023, at 20:20, Patrick McFadin wrote: > >  > A > B > C on both polls. > > Having talke

Re: [POLL] Vector type for ML

A > B > C on both polls. Having talked to several users in the community that are highly excited about this change, this gets to what developers want to do at Cassandra scale: store embeddings and retrieve them. On Tue, May 2, 2023 at 11:47 AM Andrés de la Peña wrote: > A > B > C > > I don't

Re: [DISCUSS] New data type for vector search

> > So is the goal here to provide something specific and idiomatic for the ML > community or is the goal to make a primitive that's C*-centric that then > another layer can write to? I personally argue for the former; I don't see > this specific data type going away any time soon. +1 on this

Re: Adding vector search to SAI with heirarchical navigable small world graph index

2023 at 10:53 PM Mick Semb Wever wrote: > I was soo happy when I saw this, I know many users are going to be > thrilled about it. > > > On Wed, 26 Apr 2023 at 05:15, Patrick McFadin wrote: > >> Not sure if this is what you are saying, Josh, but I believe this needs &

Re: Adding vector search to SAI with heirarchical navigable small world graph index

Not sure if this is what you are saying, Josh, but I believe this needs to be its own CEP. It's a change in CQL syntax and changes how clusters operate. The change needs to be documented and voted on. Jonathan, you know how to find me if you want me to help write it. :) As a side comment to all

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

I love the debate that surfaces occasionally, but I have to agree that KEYSPACE and SCHEMA are doing the job. There is a learning curve with Cassandra data modeling, and keywords are a minor problem. Issues that hit every user: 1. Creating the correct primary key 2. Avoiding the urge to index

Re: [DISCUSS] CEP-29 CQL NOT Operator

I love that this is finally coming to Cassandra. Absolutely hate that, once again, we'll be endorsing the use of ALLOW FILTERING. This is an anti-pattern that keeps getting legitimized. Hot take: Should we just not do Milestones 1 and 2 and wait for an index-only Milestone 3? Patrick On Thu,

Re: [VOTE] CEP-26: Unified Compaction Strategy

+1 Thanks to Lorina for getting people excited about it at Cassandra Forward! On Thu, Apr 6, 2023 at 10:37 AM Mick Semb Wever wrote: > +1 > > On Thu, 6 Apr 2023 at 19:32, Francisco Guerrero > wrote: > >> +1 (nb) >> >> On 2023/04/06 17:30:37 Josh McKenzie wrote: >> > +1 >> > >> > On Thu, Apr

Re: Google Season of Docs

It hardly feels like a loss looking at the fantastic projects that were selected. Thanks for leading this charge Lorina! Patrick On Mon, Apr 3, 2023 at 11:39 AM lorinapoland wrote: > Sadly, I am informing the community that our grant application to GSoD was > unsuccessful. > > If you would

Re: Welcome our next PMC Chair Josh McKenzie

Congrats Josh. This is an excellent acknowledgment of your awesome contributions to the Cassandra projects. Mick you left some big shoes to fill. Thank you for your service and for being an endless advocate for the project. Patrick On Fri, Mar 24, 2023 at 8:03 AM Paulo Motta wrote: > Thanks

Re: [VOTE] CEP-21 Transactional Cluster Metadata

No more nodetool createepochunsafe! +1 This is going to be another big merge. Just bookmarking the discussions last week on CEP-15. On Mon, Feb 6, 2023 at 9:57 AM Jeff Jirsa wrote: > +1 > > > On Mon, Feb 6, 2023 at 8:16 AM Sam Tunnicliffe wrote: > >> Hi everyone, >> >> I would like to start a

Re: Welcome Patrick McFadin as Cassandra Committer

5 PM, Molly Monroy wrote: >> >> Congrats, Patrick... much deserved! >> >> On Thu, Feb 2, 2023 at 1:59 PM Derek Chen-Becker >> wrote: >> >> Congrats! >> >> On Thu, Feb 2, 2023 at 10:58 AM Benjamin Lerer wrote: >> >> The PMC members are ple

Important news about Cassandra Summit

*Hello Cassandra Community,We all see what’s happening in tech right now. Cuts are being made, and budgets are frozen. For Cassandra Summit, this has translated to low sponsorship and registrations. The program committee has been discussing options with the Linux Foundation events team, and the

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

API changes are near and dear to my world. The scope of changes could be minor or major, so I think B is the right way forward. Not to throw off the momentum, but could this even warrant a separate CEP in some cases? For example, CEP-15 is a huge change, but the CQL syntax will continuously

Re: [ANNOUNCE] Evolving governance in the Cassandra Ecosystem

This is really game-changing and an important change for the Cassandra community. I would like to think that creating a governance structure like this will help get more ecosystem projects under the umbrella of Apache Cassandra. Thank you PMC, for spending the time to create this very needed

Re: [DISCUSS] Formation of Apache Cassandra Publicity & Marketing Group

rom. > > If you are a committer you can alternately use Whimsy: > https://whimsy.apache.org/committers/subscribe > > regards, > Mick > > > On Fri, 20 Jan 2023 at 00:31, Patrick McFadin wrote: > > > > > > > > > > > > > > > > > &

Cassandra Summit update for 2023-01-24

*Hello Cassandra Community!Quick take: - Register before 1/28 to get discount pricing. https://events.linuxfoundation.org/cassandra-summit/register/ - Use code CS23DS20 to get 20% off - Make sure and sign up for training the day on

Re: [DISCUSS] Formation of Apache Cassandra Publicity & Marketing Group

I would be happy to be one of the moderators. Not sure if that's singular or plural. :D Just need to know how to do it. Patrick On Fri, Jan 20, 2023 at 1:44 AM Mick Semb Wever wrote: > *To achieve this, we are proposing the formation of a Publicity & >> Marketing Working Group, and we are

[DISCUSS] Formation of Apache Cassandra Publicity & Marketing Group

*Hello Cassandra Community!We are at a pivotal moment for the Cassandra community, with the first Cassandra Summit in 7 years coming up on March 13th, and a major release coming later this year with Cassandra 5.0. It is important that we come together to set the publicity strategy and direction

Re: [DISCUSSION] Cassandra's code style and source code analysis

tyle being the source of truth continues to be untenable > and anyone still pushing for this should please engage with my earlier > points on this. > > > On 30 Nov 2022, at 04:06, Patrick McFadin wrote: > >  > I'm going to +1 what Stefan has said. I've heard on many occ

Re: [DISCUSSION] Cassandra's code style and source code analysis

I'm going to +1 what Stefan has said. I've heard on many occasions from newcomers to the project that having to use Ant is a deterrent. As a matter of fact, a few weeks ago, I spent a Sunday afternoon helping somebody trying to build Cassandra and Ant caused a ton of problems. "Ok. ant really

Cassandra Summit CFP update

orking on a submission. Thank you for being willing to create a talk! How can I help you get it completed? Again, here is my Calendly link if you need to talk it over: https://calendly.com/patrick-mcfadin/15-minute-cassandra-summit-cfp-consult <https://calendly.com/patrick-mcfadin/15-minute-cassandra-s

Speak at the Cassandra Summit

and Sharing about Best Practices And finally, I want to make sure you feel supported for any challenges you may have. I have set up a unique Calendly link if you want a quick consultation. You can choose Google Meet or Zoom and find a time that works for you. https://calendly.com/patrick-mcfadin/15

Re: Shall 4.2 become 5.0 ?

Removing JDK 8 is worth it alone. CEP-21 is going to be the real break though, and with CEP-15 tied to it, I can't see another path. Patrick On Mon, Sep 26, 2022 at 1:46 PM Caleb Rackliffe wrote: > Mick, > > Ignore me. I misread your original post. > > > > On Mon, Sep 26, 2022 at 2:01 PM

Re: CEP-15 multi key transaction syntax

to select data into a variable, let's > adopt it. > > If such syntax doesn't exist, LET (a, b, c) = (SELECT x, y, z FROM tab) is > my preference. > > On 8/22/22 19:13, Patrick McFadin wrote: > > The replies got trashed pretty badly in the responses. > When you say: &q

Re: [Discuss] CASSANDRA-17896, Gossip, and foot guns

IIRC that is something you can already change in JMX? If that's the case, I say leave that as the barrier to entry into the "parameters of doom." CEP-21 is the right path forward. It addresses the root cause instead of creating more ways to fix how you got there. This is the best thing for end

Re: CEP-15 multi key transaction syntax

ingle column results to a scalar, we > do > >>> need a way for the user to say they care whether the row was null or > the > >>> column. I think an implicit conversion here could be surprising. > However > >>> we could implement tuple expressions anyway

Re: CEP-15 multi key transaction syntax

deconstruction, which might include any of the >> following: >> >> LET (x, (y, z)) = SELECT (x, (y, z)) FROM… >> LET (x, (y, z)) = SELECT x, someTuple FROM… >> LET (x, (y, z)) = (SELECT x FROM.., SELECT y, x FROM…)) >> LET (x, (y, z)) = (someFunc(), SELECT y,

Re: CEP-15 multi key transaction syntax

> need a way for the user to say they care whether the row was null or the > column. I think an implicit conversion here could be surprising. However we > could implement tuple expressions anyway and let the user explicitly > declare v as a tuple as Caleb has suggested for the existi

Re: CEP-15 multi key transaction syntax

I'm really happy to see CEP-15 getting closer to a final implementation. I'm going to walk through my reasoning for your proposals wrt trying to explain this to somebody new. Looking at all the options, the first thing that comes up for me is the Cassandra project's complicated relationship with

Re: help for a side project

on zoom and talk it over. Here's my scheduling link: https://calendly.com/patrick-mcfadin/30min_zoom Patrick On Wed, Jun 29, 2022 at 5:13 AM Norman Menfel wrote: > Hi all, > > apologies for writing to this mailing list but I tried the user mailing > list, 2 slack channels, reddit a

Re: The Apache Cassandra(R) Corner Podcast

Apache Cassandra(R) Corner Podcast doesn't exactly flow. Why not keep the "Cassandra Corner" ? That falls under the nominative use guidelines for the Apache Foundation trademarks. Patrick On Mon, Jun 27, 2022 at 12:18 PM Nate McCall wrote: > > >> >> Are there any objections to this approach?

Re: CEP-15 multi key transaction syntax

I think the syntax is evolving into something pretty complicated, which may be warranted but I wanted to take a step back and be a bit more reflective on what we are trying to accomplish. For context, my questions earlier were based on my 20+ years of using SQL transactions across different

Re: CEP-15 multi key transaction syntax

Love the Oracle/Postgres RETURNING syntax and just generally +1 to adding INSERT and DELETE. And for each DML type... > - INSERT ... RETURNING returns inserted data (useful for defaulted or > autoincrement columns). > - UPDATE ... RETURNING returns the modified data. > - DELETE ... RETURNING

Re: CEP-15 multi key transaction syntax

Oops. I missed this part: "full primary key or a limit of 1" Still curious what the end-user would see if there is more than one row returned. On Sat, Jun 4, 2022 at 5:46 PM Patrick McFadin wrote: > I've been waiting for this email! I'll echo what Jeff said about h

Re: CEP-15 multi key transaction syntax

I've been waiting for this email! I'll echo what Jeff said about how exciting this is for the project. On the SELECT inside the transaction: In the first example, I'm making an assumption that you are doing a select on a partition key and only expect one result but is any valid CQL SELECT

Re: Adding RSS feed to the Apache Cassandra website.

+1 on option 2. Anything that eliminates a human step is how it stays up to date. On Tue, May 31, 2022 at 5:25 AM Brandon Williams wrote: > +1 to Anthony, that seems like the best path to me too. > > On Tue, May 31, 2022, 7:15 AM Anthony Grasso > wrote: > >> This is a good idea! >> >> I think

Apache Cassandra Marketing Meeting - 5/26

Hi everyone, It's been almost a month since our last meeting, and a lot is happening. 4.1 is moving along. Cassandra World Party is ready to celebrate this release, and promotions have started. We had a great turnout at the last meeting with good participation. Everyone is invited to

Re: Cassandra World Party in July; CFP open!

I'm really looking forward to this event. Last year was great and had the same casual fun as a meetup. With the addition of some in-person meetups this will be a great time to get out and meet some of your fellow Cassandra community members. An important footnote. This event is meant to coincide

Re: Appetite for a 4.1-alpha1 ?

Nothing promotable like a shiny new release tag! On Wed, May 18, 2022 at 10:50 AM C. Scott Andreas wrote: > Yep, supportive of anything that has the potential to increase the number > of users evaluating a pre-release build. Alpha sounds great. > > On May 18, 2022, at 9:29 AM, David Capwell

Apache Cassandra Marketing Meeting

Hi everyone, There are several community members working on various marketing efforts to get out the good word on Cassandra. I've been asked by a few to help facilitate a meeting where we can share and coordinate. I've taken the first step by creating a calendar item with a zoom link. When: May

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

Oh and +1 to the idea of making Apache Cassandra a company on LinkedIn. Same energy as the Twitter handle. Outgoing updates from the project. On Wed, Mar 30, 2022 at 2:41 PM Patrick McFadin wrote: > I agree that is a problem. In the past, I have tried to make these as > inclusive as po

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

I agree that is a problem. In the past, I have tried to make these as inclusive as possible by offering multiple time zones, recording every meeting, and posting it on YouTube with an email sent to dev@. What we can't substitute in a mailing list is the energy that comes from brainstorming, which

Re: New Apache Cassandra Group on LinkedIn

On Wed, Mar 9, 2022 at 12:39 PM Patrick McFadin > wrote: > >> I'm not sure if they can merge groups but from what I'm reading that >> wouldn't work either. What I'm seeing is a desire to not "promote vendors" >> which I believe is working against the project's

Re: New Apache Cassandra Group on LinkedIn

st things under Lynn's name was also an issue for us as we > wished the merits to go to the right persons. > > Now, I am sure that we can work out some solution that will benefit the > community. :-) > > Le mer. 9 mars 2022 à 15:56, Patrick McFadin a > écrit : > >>

Re: New Apache Cassandra Group on LinkedIn

I feel like this needs to be a discussion held on the public mailing list. I have been running the Apache Cassandra Users group on LinkedIn for years after taking it over from Lynn Bender. https://www.linkedin.com/groups/3803052/ We have over 7500 members and had its ups and downs but it's been

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

I'm going to put up a red flag of making config file changes of this scale on a dot release. This should really be a 5.0 consideration. With that, I would propose a #5. 5.0 nodes will only read the new config files and reject old config files. If any of you went through the config file changes

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

This is a great day for the project. These are three people that have been contributing continuously to the success of Cassandra users for so many years I can't even guess. Really makes me happy to see the project mature into a place where a diversity of contributions are recognized.

Re: [DISCUSS] Non Coding Committers

Sharan has done a good job shining a spotlight on something that has created a weird bottleneck in the project. Docs and the Cassandra website are all in-tree, but it takes somebody who probably isn't even working on those things to commit any changes. Dinesh nailed it. It's silly. I'm sure the

Re: Cassandra project biweekly status update 2022-01-03

What Ellis said. On Mon, Jan 3, 2022 at 1:48 PM Jonathan Ellis wrote: > +10 > > Could we post these on the blog as well to reach a wider audience? > > On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever wrote: > >> >> >> /wave Happy 2022 everyone! … >>> … >>> >>> It's been incredibly encouraging to

Re: Cassandra project biweekly status update 2021-11-08

Since I have been re-playing Ghost of Tsushima, I felt a Haiku would be appropriate. my cluster is failing jConsole to the rescue now I am failing On Mon, Nov 8, 2021 at 12:46 PM Joshua McKenzie wrote: > First off - Congrats again to Sumanth Pasupuleti on becoming a committer on > the

Re: Welcome Sumanth Pasupuleti as Apache Cassandra Committer

Great to see this. Congrats Sumanth! On Fri, Nov 5, 2021 at 11:34 AM Brandon Williams wrote: > Congratulations Sumanth! > > On Fri, Nov 5, 2021 at 1:17 PM Oleksandr Petrov > wrote: > > > > The PMC members are pleased to announce that Sumanth Pasupuleti has > > recently accepted the invitation

  1   2   >