[DISCUSS] CASSANDRA-20163 DELETE partition IF static column condition is currently blocked

As part of the Accord work we have been extending the harry models to support even more of the CQL domain and added more test coverage for different features; in doing so it found the following query is currently blocked — delete partition if static column is in a given state — confirmed that th

Re: [VOTE] CEP-45: Mutation Tracking

+1 > On Feb 3, 2025, at 10:33 AM, Blake Eggleston wrote: > > Hi dev@, > > I’d like to start the voting for CEP-45: Mutation Tracking > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-45:+Mutation+Tracking > Discussion: https://lists.apache.org/thread/0rstj4bzbb2596o5vw

Re: Meaningless emptiness and filtering

pport, that would preferably NOT match EMPTY >> values for the types where empty means something, like strings. For >> everything else, EMPTY could be equivalent to null and match IS NULL. >> >> The only real way to make SAI compatible with the current behavior is to add >>

Re: Meaningless emptiness and filtering

icit and - as David says - >>> inconsistent. It would be nice to move away from this as the default for a >>> variety of reasons, but also nice to make the behaviour well defined for >>> those use cases we think we’re supporting. >>> >>> On 11 Feb 2025, at 21:16

Meaningless emptiness and filtering

Bringing this discussion to dev@ rather than Slack as we try to figure out CASSANDRA-20313 and CASSANDRA-19461. In the type system, we have 2 different (but related) methods: AbstractType#allowsEmpty- if the user gives empty bytes (new byte[0]) will the type reject it Ab

Re: [DISCUSS] 5.1 should be 6.0

Given our version support… if we do make this change does this imply users must do the following to get to 6.0? 4.x upgrade to 5.0 5.0 upgrade to 6.0 So no 4.x to 6.0? Given that this is 5.1 atm we are expected to support 4.x to 5.1 upgrades, but switching to 6.0 that isn’t true based off our

Re: Supporting 2.2 -> 5.0 upgrades

From a disk format point of view the only thing I remember was the disk type bug with UDTs. Bringing that logic back was hard as the type system (in 5.0) tries to avoid allowing construction of invalid states, and we would need to weaken that in order to enable the migration. Assuming the user

Re: [DISCUSS] 5.1 should be 6.0

> My expectation is that in trunk SCM CASSANDRA_4 would change to SCM > CASSANDRA_5. Assuming you upgrade from 4.0 to 5.0, then you are running on CASSANDRA_4… how many people know that they are expected to do something about that (Sam documented the steps earlier)? What if you leave things al

Re: Supporting 2.2 -> 5.0 upgrades

assandra-sidecar), for example JMX Mbeans and other >>> interfaces. >>> >>> I think one way to do that would be to split cassandra-all into >>> cassandra-server and cassandra-common (anything used by both subprojects >>> and server), but not sur

Re: [DISCUSS] Usage of "var" instead of types in the code

+1 to allow in tests > On Jan 9, 2025, at 10:58 AM, Caleb Rackliffe wrote: > > +1 to allowing in tests for now > > On Wed, Jan 8, 2025 at 12:51 PM Mick Semb Wever > wrote: >> >> Jumping in, I'm ok to allow it in tests for a trial period too. I would >> imagine in tes

Re: Patrick McFadin joins the PMC

Congrats! > On Jan 22, 2025, at 10:06 AM, Jean-Armel Luce wrote: > > Congratulations, Patrick !! > > Le mer. 22 janv. 2025 à 18:55, Abe Ratnofsky > a écrit : >> Congrats Patrick! Well deserved. >> >>> On Jan 22, 2025, at 11:30, Ekaterina Dimitrova >>

Re: What branches should perf fixes be targeting

I think Paulo and I are in-sync on this. For me 4.x is mostly about stability right now and 5.x is more active development; so I have a higher bar for back ports to 4.x than I do to 5.x. There is also the question on “risk” which can be subjective from reviewer to reviewer. Some patches may be

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

So if you forget to update cassandra.yaml you fail the build? Makes sense to me. One additional thing I would like to see is the reverse… did you put something in yaml that isn’t in Config? This is a bug I have seen a few times…. Mostly because people don’t know the rules from SnakeYAML so ar

Re: [DISCUSS] 5.1 should be 6.0

I have not checked Jenkins, but we see this in another environment… For python upgrades have we actually audited the runtime to see that the time spent is doing real work? Josh and I have spent a ton of time trying to fix (and failing) an issue where the python driver blocks the test and we wai

Re: Capabilities

To be explicit about my concerns in the previous comments… TCM vs new table, I don’t care too much. I prefer TCM over new table, but its a preference My comment before were more about the UX of global configs. As long as we “could” (maybe per config, not every config likely needs this) allow

Re: Capabilities

orage/dissemination mechanism, this feels like an > implementation detail. > > Ideally if this is well modularized, we can always plugin or replace it with > other backends (TCM/UDP/S3/morse code/whatever) once this is functional. > > On Wed, Jan 29, 2025 at 1:17 PM David Capw

Incorrectness in SELECT and purged Cells

During fuzz testing of Accord’s CQL integration, we identified an edge case that resulted in an IndexOutOfBoundsException. This issue was reported as CASSANDRA-20108 [1]. Initially, we believed this to be a type-related problem and did not draw attention to it. However, we ensured that the work

Re: Meaningless emptiness and filtering

Talking in slack I was linked to a Go Client issue (see https://the-asf.slack.com/archives/CK23JSY2K/p1742413507980149?thread_ts=1742409054.164389&cid=CK23JSY2K and https://the-asf.slack.com/archives/C05LPRVNZV1/p1741108083834769 ) gocql was sending empty bytes until recently… > On Mar 19, 20

Re: Meaningless emptiness and filtering

Been expanding the current AST Harry tests to include collections and UDTs and been finding even more fun with vs null… what Cassandra returns is a product of the schema and what you do with the table; and these types can act differently than other types. > On Feb 13, 2025, at 4:45 AM, Mick Se

Re: Inconsistent null handling between WHERE and IF clauses

support it, we have to treat NULL like we do in IF - even if > it’s not how we want it to work. > >> On 24 Mar 2025, at 23:45, David Capwell wrote: >> >> In fuzz testing I have found some differences between `WHERE` and `IF` >> clauses that want to get feedback f

Re: [DISCUSS] How we version our releases

> Does it mean that one has to flag a feature as deprecated in the unreleased > version N, wait until when N is released (deprecating for one major cycle), > and then finally make the breaking change in N + 1? My understanding is things are not different than before, we just don’t do minors; wh

Re: [VOTE] Simplifying our release versioning process

+1 > On Apr 17, 2025, at 9:22 AM, Jon Haddad wrote: > > +1 > > On Thu, Apr 17, 2025 at 9:15 AM Josh McKenzie > wrote: >> +1 >> >> On Thu, Apr 17, 2025, at 11:58 AM, Josh McKenzie wrote: >>> [DISCUSS] thread: >>> https://lists.apache.org/thread/jy6vodbkh64plhdfwqz

Re: CEP-15 Update

; >>>>>>>>> >> >>>>>>>>> >> > On Tue, Mar 4, 2025 at 9:57 AM Dmitry Konstantinov >>>>>>>>> >> > mailto:netud...@gmail.com>> wrote: >>>>>>>>> >> >>&g

Re: [DISCUSS] How we version our releases

a software like > this, even that case doesn't really give me much heartburn. We shouldn't do > that of course, but even that extreme doesn't seem like it'd cause too much > pain. > > On Thu, Apr 17, 2025, at 2:53 PM, David Capwell wrote: >>> Does it me

Re: Welcome David Capwell as Cassandra PMC Member!

gt; >> >>> >> From: Abe Ratnofsky mailto:a...@aber.io>> >>> >> Sent: Monday, April 28, 2025 12:11:52 PM >>> >> To: dev@cassandra.apache.org <mailto:dev@cassandra.apache.org> >>> >> mailto:dev@cassandra.apache.org>> >>> >> Subject: Re: Welcome David Capwell as Cassandra PMC Member! >>> >> >>> >> Congrats David! >

Re: [VOTE][IP CLEARANCE] easy-cass-stress

+1, I am open to different names, I am cool with easy-cass-stress > On Apr 30, 2025, at 9:27 AM, Francisco Guerrero wrote: > > +1 (nb) > > On 2025/04/30 15:15:57 Jordan West wrote: >> (general@incubator cc'd) >> >> Please vote on the acceptance of the easy-cass-stress (to be renamed >> cassand

Re: Welcome David Capwell as Cassandra PMC Member!

;>> >>>> On Mon, Apr 28, 2025, at 3:09 PM, Jon Haddad wrote: >>>>> Hey everyone! >>>>> >>>>> The Project Management Committee (PMC) for Apache Cassandra is delighted >>>>> to announce that David Capwell has joined t

Re: [DISCUSS] 5.1 should be 6.0

+1 to 6.0 Strong +1 to T-3, we should support 4.0/4.1 to 6.0 upgrades. > On Apr 10, 2025, at 2:18 PM, C. Scott Andreas wrote: > > +1 6.0 > > - Scott > > — > Mobile > >> On Apr 10, 2025, at 1:34 PM, Jeremy Hanna wrote: >> >> +1 for 6.0 for TCM/Accord changes, making it easier to make a case

Re: [DISCUSS] How we version our releases

> So here's what I'm thinking: a new release strategy that doesn't use .MINOR > of semver. Goals: So we avoid 6.1, 7.2, etc? Does this imply that each release is allowed to make breaking changes (assuming they followed the “correct” deprecation process)? My first instinct is to not like this,

Re: [DISCUSS] Requirement to document features before releasing them

I wonder at what level can we enforce this. What I mean, in modeling testing I have found some odd behaviors that people were not aware of (BATCH cell resolution, NULL handling (emptiness…..), etc.)… so if documentation is dense this can help force people to think through edge cases or how 2 fe

Re: [DISCUSS] CEP-46 Finish Transient Replication/Witnesses

+1 > On May 6, 2025, at 10:53 AM, Dmitry Konstantinov wrote: > > +1 (nb) > > On Tue, 6 May 2025 at 17:32, Aleksey Yeshchenko > wrote: >> +1 >> >>> On 5 May 2025, at 23:24, Blake Eggleston >> > wrote: >>> >>> As mutation tracking relates

Re: [VOTE] Simplifying our release versioning process

> Also, I thought we had separate discussion about them - that we want to keep > up possibly with the last two LTS versions. This is what I remember as well. 6.0 would support 17/21 as thats the latest, if 7.0 is out before 25, then 7.0 would be 17/21, else it would be 21/25 > On Apr 23, 2025,

Re: Constraint's "not null" alignment with transactions and their simplification

7:47 AM, Jon Haddad wrote: >> >>  >> This looks like a really nice improvement to me. >> >> >> On Thu, Apr 10, 2025 at 7:27 AM Štefan Miklošovič > <mailto:smikloso...@apache.org>> wrote: >> Recently, David Capwell was commenting on constraint

Re: Constraint's "not null" alignment with transactions and their simplification

One argument I have against using columns in the constraint is that we currently are not able to actually handle the CHECK spec in SQL. In SQL the CHECK expression is a valid search expression (eg. price > 42 AND tag = ‘foo’), and is limited to the current row. Where we differ in Apache Cassan

Re: Welcome Ekaterina Dimitrova as Cassandra PMC member

Congrats! Very deserving! > On Mar 4, 2025, at 3:09 PM, Brandon Williams wrote: > > Congratulations Ekaterina! > > Kind Regards, > Brandon > > On Tue, Mar 4, 2025 at 2:25 PM Paulo Motta wrote: >> >> Aloha, >> >> The Project Management Committee (PMC) for Apache Cassandra is delighted to

Inconsistent null handling between WHERE and IF clauses

In fuzz testing I have found some differences between `WHERE` and `IF` clauses that want to get feedback from the broader community. If you try to query with a `null` we will reject it ``` @Test public void test() throws IOException { try (Cluster cluster = Cluster.build(1).start())

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

> I think the primary argument *against* Accord is that the syntax isn't > expressive enough to be able to address multiple conditions in MVs. For each > field that's updated, you'll need to know if you want to add that update into > the transaction, and you'd need to check if it was modified.

Re: Welcome Abe Ratnofsky as Cassandra committer!

Congrats! > On May 12, 2025, at 9:45 AM, Alex Petrov wrote: > > Hello folks of the dev list, > > The Apache Cassandra PMC is very glad to announce that Abe Ratnofsky has > accepted our invitation to become a committer! > > Abe has been actively contributing to Cassandra itself, made outstandi

Re: [VOTE] CEP-46: Finish Transient Replication/Witnesses

+1 > On May 12, 2025, at 9:26 AM, Štefan Miklošovič wrote: > > +1, great stuff, looking forward to bring it out of experimental > > On Mon, May 12, 2025 at 4:27 PM Ariel Weisberg > wrote: >> Hi dev@, >> >> I would like to start the voting for CEP-46: Finish Transient

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

> The MV repair tool in Cassandra is intended to address inconsistencies that > may occur in materialized views due to various factors. This component is the > most complex and demanding part of the development effort, representing > roughly 70% of the overall work. > but I am very concerned ab

Re: CASSANDRA-20490 Question about broken forced ephemeral snapshots during repair

> "force" can be true / false. When true, then it will not check if a snapshot > exists My mental node for “force” was only to deal with down nodes, and nothing to do with snapshots… so this feels like a weird behavior @Option(title = "force", name = {"-force", "--force"}, description = "Use

Re: CASSANDRA-20490 Question about broken forced ephemeral snapshots during repair

inisticId is basically unique? I see it is created from parent id, session id, keyspace, table and ranges. I do not think there would ever be two cases of snapshots like that with exact same values.WDYT?RegardsOn Mon, May 12, 2025 at 6:55 PM David Capwell <dcapw...@apple.com> wrote:> &qu

<    1   2   3   4