[
https://issues.apache.org/jira/browse/CASSANDRA-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074571#comment-14074571
]
Aleksey Yeschenko commented on CASSANDRA-7370:
----------------------------------------------
First, let me say that I don't have an issue w/ the code itself, it's okay,
other than a few code style issues (no newlines before opening brackets, etc.)
The reflection approach doesn't make it impossible to accidentally forget a new
property though, mostly because you can still forget to call configChanged() in
a new DD accessor method, but makes the table structure unnecessarily obscure.
I'm in favor of an explicitly defined table here.
Also, not sure what the story is for writes (currently you can just write to
the node_config table and change anything, and the table would start returning
incorrect data).
Therefore we should probably wait until 3.0, for CASSANDRA-7622 or something
like it, that would allow us to map column names to methods in a clean way.
> 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
> Assignee: Robert Stupp
> Priority: Minor
> Labels: ponies
> Attachments: 7370-v3.txt
>
>
> 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)
