As this is a major change including structural aspects as well as the separation of feature configuration, it came to my mind, why do we stuck with YAML as envelope? Many aspects already in discussion may be covered with already existing tools. Would it worth considering, e.g. Typesafe Config as an alternative for a new approach to Cassandra configuration?
> On 17. Feb 2022, at 23:13, Caleb Rackliffe <calebrackli...@gmail.com> wrote: > > Hey everyone, > > There has already been some Slack discussion > <https://the-asf.slack.com/archives/CK23JSY2K/p1645033339547749> around this, > but for anyone who doesn't follow that closely, I'd like to lobby more widely > for my proposal in CASSANDRA-17292 > <https://issues.apache.org/jira/browse/CASSANDRA-17292> to eventually move > cassandra.yaml toward a more nested structure. > > The proposal itself is here > <https://github.com/maedhroz/cassandra/commit/450b920e0ac072cec635e0ebcb63538ee7f1fc5a>, > and there has already been some inline discussion, but feel free to drop any > feedback there, in the Jira, or here, depending on what you're most > comfortable with. > > Given where we are in the lead-up to 4.1, I have no intention of pushing to > adopt any of this for existing config in that release. However, what I think > would be nice is if we could come to a rough consensus in time to inform work > on new parameters, like those we're planning to add in CASSANDRA-17188 > <https://issues.apache.org/jira/browse/CASSANDRA-17188>. > > Thanks!
