Re: [DISCUSS] Nested YAML configs for new features

Isn't one of the primary reasons to have a YAML configuration instead of a properties file is to allow typed and structured (implies nested) configuration? I think it makes a lot of sense to group related configuration options (e.g. a feature) into a typed class when we're talking about more than

Re: [DISCUSS] Mentoring newcomers

Thank you Benjamin. I would like to suggest to add that information also to our web page under Community when the tickets are resolved. I can work on that when the time comes. Have a great day Ekaterina On Mon, 22 Nov 2021 at 8:53, Benjamin Lerer wrote: > Thank you very much for volunteering. >

Re: [DISCUSS] Mentoring newcomers

Thank you very much for volunteering. I have opened a JIRA to create a *mentors *alias on the CASSANDRA project ( INFRA-22555 ) and another ticket to create a *cassandra_mentors* user group in slack ( INFRA-22556

Re: [VOTE] CEP-17: SSTable format API

The vote passes with 13 +1 votes and no -1 votes. Thanks to everyone. Regards, Branimir On Thu, Nov 18, 2021 at 8:46 PM Dinesh Joshi wrote: > +1 > > > On Nov 17, 2021, at 1:22 AM, Benjamin Lerer wrote: > > > > +1 > > > > Le mar. 16 nov. 2021 à 18:05, Joshua McKenzie a > > écrit : > > > >>

Re: [DISCUSS] Nested YAML configs for new features

I do not have a strong opinion for one or the other but wanted to raise the issue I see with the "Settings" virtual table. Currently the "Settings" virtual table converts nested options into flat options using a "_" separator. For those options it allows a user to query the all set of options