I am not familiar with ECS but if we’re going to go for it I would prefer it to be a sub project really. Jon, what do you think?
On Thu, Apr 25, 2024 at 2:44 PM Brandon Williams <dri...@gmail.com> wrote: > I want to begin by saying I am generally +1 on this because I have > become a fan of easy-cass-stress after using it, but I am curious if > this is intended to be a subproject, or replace cassandra-stress? If > the latter, we are going to have to reconcile the build systems > somehow. I don't really want to drag ECS back to ant, but I also > don't want two different build systems in-tree. > > Kind Regards, > Brandon > > On Thu, Apr 25, 2024 at 9:38 AM Jon Haddad <j...@jonhaddad.com> wrote: > > > > I've been asked by quite a few people, both in person and in JIRA [1] > about contributing easy-cass-stress [2] to the project. I've been happy to > maintain the project myself over the years but given its widespread use I > think it makes sense to make it more widely available and under the > project's umbrella. > > > > My goal with the project was always to provide something that's easy to > use. Up and running in a couple minutes, using the parameters to shape the > workload rather than defining everything through configuration. I was > happy to make this tradeoff since Cassandra doesn't have very many types of > queries and it's worked well for me over the years. > > > > Obviously I would continue working on this project, and I hope this > would encourage others to contribute. I've heard a lot of good ideas that > other teams have implemented in their folks. I'd love to see those ideas > make it into the project, and it sounds like it would be a lot easier for > teams to get approval to contribute if it was under the project umbrella. > > > > Would love to hear your thoughts. > > > > Thanks, > > Jon > > > > [1] https://issues.apache.org/jira/browse/CASSANDRA-18661 > > [2] https://github.com/rustyrazorblade/easy-cass-stress >
