[
https://issues.apache.org/jira/browse/CASSANDRA-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415185#comment-17415185
]
Aleksei Zotov commented on CASSANDRA-16914:
-------------------------------------------
[~samt]
Thanks for the response! You brought a very good point. In my opinion, VTs are
more about _content_ since they are still tables in the first place and their
general intention is to represent some data. Therefore, I though from the
perspective of _contents_ rather than _commands_.
A few more arguable points:
# If we follow the same structure as {{nodetool}} commands have then 4 tables
will have 1 column (role) and 1 table will have 2 columns (role+resource). I
believe it seems to be weird for operators since that does not really represent
content and it is not obvious what to do with these tables. The only way to
make it logic is to have a representative table name. However, I could not come
up with a name I like, smth like _invalidation_permissions_cache_ still looks
weird.
# As for me, it is not mandatory to follow the same structure as we have in
{{nodetool}} commands. I'm not proposing to have completely different
functionality, but having a bit more flexible functionality in VTs does not
seem to be an issue, does it? Is there a requirement/assumption that both
should work identically?
# Regarding the difference between VTs and auth tables - I agree with your
point and I'd rather add a few more columns to _roles_cache_ (that's the only
one that does not have all data available in auth caches) than keeping only
keys necessary for dropping caches.
Curious to hear your opinion.
> Implement Virtual Tables for Auth Caches
> ----------------------------------------
>
> Key: CASSANDRA-16914
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16914
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization, Feature/Virtual Tables
> Reporter: Aleksei Zotov
> Assignee: Aleksei Zotov
> Priority: Low
> Fix For: 4.x
>
>
> {{NodeTool}} commands for Auth Caches invalidation were implemented as a part
> of CASSANDRA-16404 ticket. While discussing that ticket it was agreed that
> there is a need to develop the same kind of functionality through Vitrual
> Tables. Unfortunately, VT did not have {{TRUNCATE}} and {{DELETE}} support.
> And CASSANDRA-16806 was created for that reason. Once it is completed,
> further work can be started.
> The goal of this ticket is to create VTs for the following caches:
> * {{CredentialsCache}}
> * {{JmxPermissionsCache}}
> * {{NetworkPermissionsCache}}
> * {{PermissionsCache}}
> * {{RolesCache}}
> The VTs should support reading from and modification of the in the Auth
> Caches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
