Re: [VOTE] Release dtest-api 0.0.17

2024-09-16 Thread Doug Rohrer
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 > pointed out

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

2024-09-16 Thread Caleb Rackliffe
The patches for this issue have gotten a +1 from Mick, and that meets our strict 2 committer rule, but I'm posting them here in case anyone else wants take a look: 4.0: https://github.com/apache/cassandra/pull/3526 4.1: https://github.com/apache/cassandra/pull/3539 5.0: https://github.com/apache/c

[DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-16 Thread Štefan Miklošovič
We are using a library called Chronicle Queue (1) and its dependencies and we ship them in the distribution tarball. The version we use in 5.0 / trunk as I write this is 2.23.36. If you look closely here (2), there is one more release like this, 2.23.37 and after that all these releases have "ea"

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-16 Thread Jordan West
Thanks for the sleuthing Stefan! This definitely is a bit unfortunate. It sounds like a replacement is not really practical so I'll ignore that option for now, until a viable alternative is proposed. I am -1 on us writing our own without strong, strong justification -- primarily because I think the

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-16 Thread Benedict
Don’t we essentially just use it as a file format for storing a couple of kinds of append-only data?I was never entirely clear on the value it brought to the project.On 16 Sep 2024, at 22:11, Jordan West wrote:Thanks for the sleuthing Stefan! This definitely is a bit unfortunate. It sounds like a

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-16 Thread Josh McKenzie
I think it's FQLTool only right now; I bumped into it recently doing the JDK21 compat work. I'm not concerned about current usage / dependency, but if our usage expands this could start to become a problem and that's going to be a hard thing to track and mange. So reading through those issues

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

2024-09-16 Thread Brandon Williams
My concern is that we have to keep making sure it's not phoning home(1,2). (1) https://issues.apache.org/jira/browse/CASSANDRA-18538 (2) https://issues.apache.org/jira/browse/CASSANDRA-19656 Kind Regards, Brandon On Mon, Sep 16, 2024 at 7:53 PM Josh McKenzie wrote: > > I think it's FQLTool only