[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-11695:
------------------------------------------
Test and Documentation Plan: CI to be done
Status: Patch Available (was: Open)
[~maulin.vasavada] I have tried to extract more of that here (1)
Your work was very nice to incorporate into this. I am not completely sure if
want to really move it all to cassandra.yaml. The patch I did works in such a
way that if nothing is in yaml, it takes config from cassandra-env.sh. I
consider this to be a little bit more convenient because people can continue to
configure it as they are used to but if they want to do it all via yaml, they
just need to uncomment the respective section in yaml and the config would be
taken from there.
I will try to reach ML with a question whether this is OK to do. I consider
"move it all to yaml" quite disruptive.
(1) https://github.com/apache/cassandra/pull/3708/files
> Move JMX connection config to cassandra.yaml
> --------------------------------------------
>
> Key: CASSANDRA-11695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11695
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Sam Tunnicliffe
> Assignee: Stefan Miklosovic
> Priority: Low
> Labels: lhf
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since CASSANDRA-10091, we always construct the JMX connector server
> programatically, so we could move its configuration from cassandra-env to
> yaml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
