[ https://issues.apache.org/jira/browse/CASSANDRA-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039248#comment-14039248 ]
Tupshin Harper commented on CASSANDRA-7370: ------------------------------------------- i'm +1 on abusing the system with virtual/phantom tables. they are a well established rdbms pattern that is conceptually simple (albeit not particularly elegant) and well understood. reflection could be leveraged to eliminate the need to keep an up to date list > Create a new system table "node_config" to load cassandra.yaml config data. > --------------------------------------------------------------------------- > > Key: CASSANDRA-7370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7370 > Project: Cassandra > Issue Type: Wish > Components: Config > Reporter: Hayato Shimizu > Priority: Minor > Labels: ponies > > Currently the node configuration information specified in cassandra.yaml can > only be viewed via JMX or by looking at the file on individual machines. > As an administrator, it would be extremely useful to be able to execute > queries like the following example; > select concurrent_reads from system.node_config; > which will list all the concurrent_reads value from all of the nodes in a > cluster. > This will require a new table in the system keyspace and the data to be > loaded (if required) during the bootstrap, and updated when MBeans attribute > value updates are performed. The data from other nodes in the cluster is also > required in the table. -- This message was sent by Atlassian JIRA (v6.2#6252)