I wouldn't oppose making things more well defined there. Kind Regards, Brandon
On Fri, Jan 24, 2025 at 8:22 AM Štefan Miklošovič <smikloso...@apache.org> wrote: > > If that is the case, we could have something like this? > > @HiddenInYaml > public boolean auto_bootstrap = true; > > Then a build-time check would parse Config.java on these annotations etc and > skip that if it is not in yaml. > > It is OK if we decide not to expose but we should have some basic overview > about that and be sure it was not added into yaml by mistake. > > > On Fri, Jan 24, 2025 at 3:19 PM Brandon Williams <dri...@gmail.com> wrote: >> >> I think those are things we've decided we don't want to expose to the >> average user, like auto_bootstrap. >> >> Kind Regards, >> Brandon >> >> On Fri, Jan 24, 2025 at 8:16 AM Štefan Miklošovič >> <smikloso...@apache.org> wrote: >> > >> > Hello, >> > >> > from time to time I see configuration properties in Config.java and they >> > are clearly not in cassandra.yaml. Not every property in Config is in >> > cassandra.yaml. I would like to know if there is some specific reason >> > behind that. >> > >> > Question related to that is if we could not have a build-time check that >> > all properties in Config have to be in cassandra.yaml and fail the build >> > if a property in Config does not have its counterpart in yaml. >> > >> > There are dozens of properties in Config and I have a strong suspicion >> > that we missed to publish some to yaml so users do not even know such a >> > property exists and as of now we do not even know which they are.
