The current cassandra-stress is in poor condition and clocks in at a hefty 16k lines of Java code. I was involved in some work with it last Summer (CASSANDRA-18529) and it was tricky.
I'm strongly in favor of replacing it with a modern tool which is easier to configure and more user friendly. While it's a valid concern to ask who might help maintain it, the same could be asked about the existing cassandra-stress which has not been well maintained recently. A separate subproject like dtest and the Java driver would maybe help address concerns with introducing a gradle build system and Kotlin. On Fri, Apr 26, 2024 at 2:30 PM Jon Haddad <j...@jonhaddad.com> wrote: > @mck I haven't done anything with IP clearance. Not sure how to, and I > want to get a feel for if we even want it in the project before I invest > time in. Jeff's question about people willing to maintain the project is a > good one and if people aren't willing to maintain it with me, it's only > going to make my life harder to move under the project umbrella. I don't > want to go from my wild west style of committing whatever I want to waiting > around for days or weeks to get features committed. > > > Project rename happened here: > > commit 6c9493254f7bed57f19aaf5bda19f0b7734b5333 > Author: Jon Haddad <j...@jonhaddad.com> > Date: Wed Feb 14 13:21:36 2024 -0800 > > Renamed the project > > > > > > On Fri, Apr 26, 2024 at 12:50 AM Mick Semb Wever <m...@apache.org> wrote: > >> >> >> On Fri, 26 Apr 2024 at 00:11, Jon Haddad <j...@jonhaddad.com> wrote: >> >>> I should probably have noted - since TLP is no more, I renamed >>> tlp-stress to easy-cass-stress around half a year ago when I took it over >>> again. >>> >> >> >> Do we have the IP cleared for donation ? >> At what SHA did you take and rename tlp-stress, and who was the copyright >> holder til that point ? >> We can fix this I'm sure, but we will need the paperwork. >> >> >>
