Re: [DISCUSS] Lift MessagingService.minimum_version to 40 in trunk

2023-07-14 Thread Mick Semb Wever
> > I am pretty strongly in favor just to keep the amount of code kept around > for serialization/deserialization and caching serialized sizes for > different versions under control. > Thanks Ariel. CASSANDRA-18314 is patched, and looking for reviewers.

Re: Writes after the column is dropped, broken reads, and TCM

2023-07-14 Thread Jakub Zytka
I would like to propose the following solution to CASSANDRA-17047, CASSANDRA-18589, CASSANDRA-18591 etc. (the rationale and line of thought included below) for pre-TCM Cassandra versions, and I'd love to hear your feedback. Definitions: There are three states of knowledge of a node wrt to a partic

Re: Changing the output of tooling between majors

2023-07-14 Thread German Eichberger via dev
+1 to always version the output format From: Dinesh Joshi Sent: Thursday, July 13, 2023 3:36 PM To: dev Subject: [EXTERNAL] Re: Changing the output of tooling between majors This adds maintenance overhead but is a potential alternative. I would only flip the fl

Re: Changing the output of tooling between majors

2023-07-14 Thread Aleksey Yeshchenko
As Eric said, a major release is not a license to make externally visible breaking changes. We are too mature a project now. I have OCD tendencies like many people here, but one must learn to live with aesthetically imperfect tool output. Internal changes are fine, external changes that are act