Hi all,
I am analyzing how memory allocation is organized in Cassandra (4.x-5.x)
and have a question about memory allocators usage in Apache Cassandra code.
Some time ago Cassandra-specific networking_cache has been introduced (
https://issues.apache.org/jira/browse/CASSANDRA-15066 +
https://issu
I believe that opens the door to this kind of situations:
1. create superuser role "role1"
2. create superuser role "role2"
3. add "role2" to members of "role1"
4. remove "role2" from the members of "role1"
5. "role2" now inexplicitly lost the superuser state
TBH, my preferred solution is making
Why don't we just update the is_superuser column of a role when it
effectively achieves a superuser status when it is granted some superuser
role? Similarly, we would remove its superuser status when there are no
superuser roles granted to it anymore.
I think that at least for the second case (whe
Hi Maxwell,
Currently system_auth.roles table doesn’t have acquired superuser info
available in columns to filter on it. Below is the system_auth.roles table for
the example I have listed in the previous email. If you notice, though role1
and role11 acquired superuser status through grants, is_
