JIRA Label for Client-Impacting Changes/Decisions

As a Cassandra driver developer, I'm looking for a good way to keep track of client-impacting changes and decisions in Cassandra. I'm aware of super tasks like CASSANDRA-8043 (native v4), and others (schema migration

unable to get saved data after successfully calling batch_mutate

Hi, I met an issue that cassendra can't save some data, but can save others. I call batch_mutate to save user's (uid 51122) data, it returns success. But when i get it, it returns empty But other user (uid 22) , for the same operation, it can return data. It's so weird. could you help me for my pr