As long as the implemented nodetool commands are still going over JMX I see no issue.
The problem lies when you need native transport access. In a secured cluster you possibly need an entirely new set of access information (username, password, ssl certificate) depending on how JMX access and native transport access are setup. You also possibly need access to different ports allowed if the admin client is remote. I think it is burdensome on the end user if we require them to have both JMX and native transport setup and configured for operational access and then also to know which set of access information to use on a per command basis. -Jeremiah > On Jul 15, 2021, at 2:59 PM, Brandon Williams <dri...@gmail.com> wrote: > > On Thu, Jul 15, 2021 at 8:59 AM Paulo Motta <pauloricard...@gmail.com> wrote: >> >> Perhaps one approach to expose VirtualTables via nodetool without requiring >> the user to provide CQL credentials would be to provide a generic >> StorageServiceMBean.queryVirtualTable(String name) JMX method returning a >> TabularData result. This would allow to keep a consistent nodetool frontend >> to users while progressively switching the backend from JMX to >> VirtualTables. > > I like this idea. +1 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
