[ https://issues.apache.org/jira/browse/CASSANDRA-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315516#comment-17315516 ]
Benjamin Lerer commented on CASSANDRA-16404: -------------------------------------------- [~sumanth.pasupuleti] I reassigned the tiket to [~azotcsit] as he provided a patch for that ticket. I hope it is fine with you. [~azotcsit] Thanks a lot for the patch, I might not be able to review it properly before a couple of week. I had a quick look at your patch and one thing that would be gret is if you could had some unit tests to test the behavior of the changes. > Provide a nodetool way of invalidating auth caches > -------------------------------------------------- > > Key: CASSANDRA-16404 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16404 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Authorization > Reporter: Sumanth Pasupuleti > Assignee: Alexey Zotov > Priority: Normal > Fix For: 4.x > > Time Spent: 20m > Remaining Estimate: 0h > > We currently have nodetool commands to invalidate certain caches like > KeyCache, RowCache and CounterCache. > Being able to invalidate auth caches as well can come in handy in situations > where, critical backend auth changes may need to be in effect right away for > all the connections, especially in configurations where cache validity is > chosen to be for a longer duration. An example can be that an authenticated > user "User1" is no longer authorized to access a table resource "table1" and > it is vital that this change is reflected right away, without having to wait > for cache expiry/refresh to trigger. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org