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.

Reply via email to