[ https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450773#comment-17450773 ]
David Capwell commented on CASSANDRA-15254: ------------------------------------------- bq. May be we should also discuss this point in the current on going dev discussion. I would hope we can avoid that; dev@ threads can get derailed too quickly and halt any and all progress. bq. unifying the data logged by Config and exposed by the VirtualTable is was also taking into account sensible data through some new annotation and ignoring deprecated config settings. Cool, glad to know we were thinking similar thoughts. bq. I did not realized that we intended to change that Not change, but support in a cleaner way. Right now getters/setters are supported, but you need to make them snake cased as SnakeYAML doesn't support changing that (Jackson does); so the following works today {code} private String foo; private String moreComplex; public getFoo() { return foo; } public setFoo(String v) { foo = v; } // ugly public getMore_complex() { return moreComplex; } public setMore_complex(String v) { moreComplex = v;} {code} One concern that gets brought up is that setter validation gets duplicated as we can't block in 1 consistent way, by fixing the getter/setter camel -> snake case thing, we can avoid this problem when we feel its best to. > Allow UPDATE on settings virtual table to change running configurations > ----------------------------------------------------------------------- > > Key: CASSANDRA-15254 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15254 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables > Reporter: Chris Lohfink > Assignee: Benjamin Lerer > Priority: Normal > > Allow using UPDATE on the system_views.settings virtual table to update > configs at runtime for the equivalent of the dispersed JMX > attributes/operations. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org