The problem with scoping this to “features” is that we end up with at best
local coherence. The config file as a whole will end up just as incoherent
through its design evolution as it has historically.
If you take a look at my proposed layout for the overall config, there is a
“limits” section
“
IMO 15234 has sailed – it’s been held up for a long time, and was brought
to this list for discussion with no engagement. Ekaterina is long overdue
being able to commit her work. “
Sailed? I submitted the patch a week ago for review. Not sure how to
understand this statement. Can elaborate, pl
I mean that it has been waiting for months, is ready to go, and I don’t want to
hold you up any longer.
From: Ekaterina Dimitrova
Date: Tuesday, 30 November 2021 at 13:44
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Nested YAML configs for new features
“
IMO 15234 has sailed – it’s been
Thank you for confirming as I misread your email at first :-)
I had a chat with David last week and I don’t think his plan is reworking
of 15234 but incremental improvements on top of it.
Regarding config, after spending time cleaning around and looking more into
detail my only appeal is:
- Central
