Re: [DISCUSS] Donating easy-cass-stress to the project

Clarification - there would be some real value in donating easy-cass-stress (as the subject says), not lab… The demo was about easy-cass-lab, which uses easy-cass-stress. Thanks, Doug > On Oct 8, 2024, at 1:51 PM, Doug Rohrer wrote: > > Hey folks, > > I just wanted to

Re: [DISCUSS] Donating easy-cass-stress to the project

hanks!) - Some form of IP clearance would need to be done if this were to move forward. It seems the major concerns other than IP clearance were taken care of in the thread. Is there an appetite to bring easy-case-stress into the Apache umbrella and, if so, how would we move forward from here?

Re: [DISCUSS] Donating easy-cass-stress to the project

Hey folks,I just wanted to resurface this conversation, especially after Jon and Jordon’s talk at Community over Code this week. I think there would be some real value in getting easy-cass-lab donated and part of the ecosystem.To try to summarize:- Jon would like to donate if his active development

Re: [VOTE] Release dtest-api 0.0.17

Vote passes with 6 binding a 4 non-binding (accidentally added myself to the “binding” count before). Thanks all. I’ll get the release out ASAP. Doug > On Sep 11, 2024, at 5:32 PM, Doug Rohrer wrote: > > As it stands, the vote passes with 7 binding and 3 non-binding +1s. Dinesh

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

+1 on rejection-by-default, for several reasons: 1) Jordan’s point on the fact that recovery from this kind of data misplacement is very difficult. 2) Without any sort of warning or error in existing Cassandra installations, how many operators/users would actually know that they have been hit by

Re: [VOTE] Release dtest-api 0.0.17

On Sep 10, 2024, at 5:16 PM, Doug Rohrer wrote: > > It was pointed out that auto-correct removed the “d” from “dtest” so just > responding to this with a correct title in case “test-api” wasn’t clear. Vote > will still close at the initial 24-hour period as I don’t think this h

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

Congrats folks - well deserved. Doug > On Aug 30, 2024, at 4:18 PM, Jon Haddad wrote: > > The PMC's members are pleased to announce that Jordan West and Stefan > Miklosovic have accepted invitations to become PMC members. > > Thanks a lot, Jordan and Stefan, for everything you have done for t

Re: Welcome Doug Rohrer as Cassandra Committer

Thanks Dinesh (and everyone else!). Doug > On Aug 23, 2024, at 2:55 PM, Dinesh Joshi wrote: > > 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, Sideca

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

+1 (nb) > On Aug 4, 2024, at 2:18 AM, Yifan Cai wrote: > > Hi, > > I am proposing backporting CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0. > > There is a discussion thread > on the > topic. In summary, the backport would b

Re: [VOTE] CEP-42: Constraints Framework

+1 (nb) - Thanks for all of the suggestions and Bernardo for wrangling the CEP into shape! Doug > On Jul 1, 2024, at 3:06 PM, Dinesh Joshi wrote: > > +1 > > On Mon, Jul 1, 2024 at 11:58 AM Ariel Weisberg > wrote: >> Hi, >> >> I am +1 on CEP-42 with the latest updat

Re: [DISCUSS] CEP-42: Constraints Framework

On the Analytics side, as long as the CQLSSTableWriter understands and enforces the constraints (which it should be able to , given we provide the table schema) we should be good to go. We should try hard to avoid scanning the data on import, as the Analytics library does a bunch of things to pu

Re: [DISCUSS] CEP-42: Constraints Framework

To your point about Guardrails vs. Constraints, I do think the distinct roles of “cluster operator” and “application developer” help show how these two frameworks are both valuable. I don’t think I’d expect a cluster operator to be involved in every table design decision, but being able to set w

Re: [DISCUSS] CEP-42: Constraints Framework

There’s a difference between the two though. Constraints are part of the table schema, and (independent of the interaction with Guardrails), have no dependency on yaml files being perfectly in sync across the cluster. Therefore, the feature (Constraints) on its own doesn’t depend on configuratio

Re: [DISCUSS] CEP-42: Constraints Framework

To me, the difference between system-level guardrails and table-level constraints is the difference between operational concerns (guardrails) and business concerns (table-level constraints). The two things are only related to one another because they both may limit the value of a field in some w

Re: [DISCUSS] CASSANDRA-19113: Publishing dtest-shaded JARs on release

+1 (nb, but not a vote, so ¯\_(ツ)_/¯ ) - would be lovely to not have to deal with this individually for each project in which we use the in-jvm dtest framework. As Francisco noted, we’re using this in the sidecar and Analytics projects now and I’ve had to jump through a lot of hoops to get every

Re: CASSANDRA-18941 produce size bounded SSTables from CQLSSTableWriter

+1 (nb) - wiłl be nice for the analytics writer to be able to size SSTables appropriately and efficiently. Doug > On Oct 24, 2023, at 10:36 PM, guo Maxwell wrote: > > 😄 > > Chris Lohfink mailto:clohfin...@gmail.com>> > 于2023年10月25日周三 05:02写道： >> +1 >> >> On Tue, Oct 24, 2023 at 11:24 AM Bra

Re: [DISCUSS] putting versions into Deprecated annotations

+1 on reason string, especially some way to indicate what replaces a method if it’s being moved into some other class/new method with more parameters/etc. I’ve found lots of cases (in code bases in general, not C* in particular) where something is marked as Deprecated but there’s no mention of a

Re: [VOTE] Accept java-driver

+1 (nb) > On Oct 3, 2023, at 10:37 AM, C. Scott Andreas wrote: > > +1 (nb) > > Accepting this donation would mark a huge milestone for the project. > >> On Oct 3, 2023, at 4:25 AM, Josh McKenzie wrote: >> >> >>> I see now this will likely be instead apache/cassandra-java-driver >> I was won

Re: [Discuss] Enabling JMX in in-jvm dtests (by default)

I’d agree that anywhere we’re calling `nodetoolResult` or `nodetool` in a test, it would be better to enable JMX and use it rather than the older mocks we set up to enable calling the mbeans directly. I don’t think enabling JMX by default is the right way to go mostly due to the added resources/

Re: [DISCUSS] CASSANDRA-18743 Deprecation of metrics-reporter-config

My only concern about removal in 5.1 would be that removing it in a “minor” release would really be a breaking change, and semver says that should happen in a major version. If we really want to be semver compliant, it shouldn’t be removed until 6.0 (or, if we remove it in the next release, we

Re: [VOTE] Release dtest-api 0.0.16

+1 (nb) - Thanks Dinesh! Doug > On Aug 16, 2023, at 5:34 PM, Dinesh Joshi wrote: > > Proposing the test build of in-jvm dtest API 0.0.16 for release. > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git > > Candidate SHA: > https://github.com/apache/cassandra

Re: [VOTE] Release dtest-api 0.0.15

+1 (nb) > On May 24, 2023, at 11:32 AM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > > On Wed, May 24, 2023 at 10:31 AM Dinesh Joshi wrote: >> >> Proposing the test build of in-jvm dtest API 0.0.15 for release. >> >> Repository: >> https://gitbox.apache.org/repos/asf?p=cassa

Re: [VOTE] Release dtest-api 0.0.14

+1 (nb) Doug Rohrer > On May 15, 2023, at 7:17 PM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > >> On Mon, May 15, 2023 at 5:12 PM Dinesh Joshi wrote: >> >> Proposing the test build of in-jvm dtest API 0.0.14 for release. >>

Re: [VOTE] CEP-29 CQL NOT Operator

+1 (nb) > On May 8, 2023, at 4:52 AM, 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. www.datastax.com

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

improving it. Doug Rohrer > On May 6, 2023, at 1:52 PM, Dinesh Joshi wrote: > > +1 > >> On May 4, 2023, at 9:46 AM, Doug Rohrer wrote: >> >> Hello all, >> >> I’d like to put CEP-28 to a vote. >> >> Proposal: >> >> https://cwiki.apa

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

there are at least three binding +1s and no binding vetoes. Thanks, Doug Rohrer

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

> On Apr 5, 2023, at 11:18 AM, Doug Rohrer wrote: > > Sorry for the delay in responding here - yes, we can add some diagrams to the > CEP - I’ll try to get that done by end-of-week. > > Thanks, > > Doug > >> On Mar 28, 2023, at 1:14 PM, J. D. Jordan wrote: >

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

Sorry for the delay in responding here - yes, we can add some diagrams to the CEP - I’ll try to get that done by end-of-week. Thanks, Doug > On Mar 28, 2023, at 1:14 PM, J. D. Jordan wrote: > > Maybe some data flow diagrams could be added to the cep showing some example > operations for read

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

I agree that the analytics library will need to support vnodes. To be clear, there’s nothing preventing the solution from working with vnodes right now, and no assumptions about a 1:1 topology between a token and a node. However, we don’t, today, have the ability to test vnode support end-to-end

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

keep the discussion here on the dev list vs. in the wiki, as we’ve found it easier to manage via email. Sincerely, Doug Rohrer & James Berragan

Please grant Wiki access for CEP

Hi folks: I’d like to post a CEP, but given it’s the first time I’m trying to contribute to the wiki, I don’t have access. If someone with access could please grant user drohrer access to post, I’d greatly appreciate it. Thanks, Doug Rohrer