[
https://issues.apache.org/jira/browse/CASSANDRA-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380539#comment-17380539
]
Sam Tunnicliffe commented on CASSANDRA-16404:
---------------------------------------------
Yep, I completely recognise your points here [~blerer], but I suppose my
general counter argument would be if not now, when?
{quote}I also want to raise the fact that so far the Virtual Tables that we
expose do not support updates. The mechanism is there but has not really been
used (TRUNCATE is not supported at at).
{quote}
This is a brand new, low risk feature which is not blocking a release and nor
is it particularly urgent. That seems to me to make it an ideal way to explore
& flesh out that area.
{quote}Will it not make sense to support both approach until Virtual Tables
provide the same level of functionalities that JMX and NodeTool or an extended
version?
{quote}
That is quite an ambitious goal. My concern is that if we take the approach of
splitting each task like this into distinct tickets, then pragmatism will get
the better of us as it has in the past. That is, the desire for something that
"does the job" today trumps the better/newer, but ultimately redundant, stuff.
i.e. if there's a way to acheive this through nodetool/JMX, the incentive to
build the VT version largely disappears.
All that said, like I said before I do appreciate that a lot of work has
already gone into this ticket so it's absolutely my bad for not bringing
forward this suggestion earlier. Aside from the syntactic stuff I mentioned in
my previous comment, this generally LGTM, so I certainly wouldn't dig my heels
in over it should we choose to stick with the current approach.
> 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: Aleksei Zotov
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 50m
> 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: [email protected]
For additional commands, e-mail: [email protected]
