On Wed, Dec 18, 2024 at 11:50 AM Paul Chandler <p...@redshots.com> wrote:
> > This is all old history and has been fixed, so is not really what the > question was about, however these old problems have a bad legacy in the > memory of the people that matter. Hence the push back we have now. > I totally understand this type of push back. There are many operators of Cassandra and each with their own way of doing things with their own internal tooling. Some folks are more insulated than others from issues that you're describing here – not due to any other reason but because their tooling is mature so some of these issues do not register as 'operator pain'. > I would like to thank Jeff for pointing out that my pain could be > legitimate, but I would also like to thank everyone else for answering too. > The Cassandra community is very keen to learn about these issues and do something to fix them. Thank you for starting this thread. It helps shine light on these issues. Mailing list threads and JIRAs help the community immensely. cheers, Dinesh
