Just wondering when 3.0.11 will be released?
Thanks,
Johnny
Hello 👋
We would like to propose CEP-51: Support Include Semantics for
cassandra.yaml for adoption by the community:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-51+Support+Include+Semantics+for+cassandra.yaml
This CEP proposes adding completely optional include directives to
Cassand
Another possible idea for this - we could support env variables on the
includes eg
include_if_exists: conf/environments/${ENVIRONMENT}.yaml
This would be quite useful I think?
On Fri, 18 Jul 2025 at 19:57, Johnny Miller
wrote:
> Hello 👋
>
> We would like to propose CEP-51: Suppor
ng on non-classified configuration
> parameters could tighten the whole thing up and give us a minimally
> invasive way to support both through a transition.
>
> On Mon, Jul 21, 2025, at 9:41 AM, Johnny Miller wrote:
>
> I have added the section "Reference Example Configuration&qu
both new and old users. Starting with examples of the
> new paradigm and then refactoring config out over time for the default
> config is a path forward I'd support.
>
> On Mon, Jul 21, 2025, at 9:18 AM, Johnny Miller wrote:
>
> One feature I was thinking of adding to the CEP
One feature I was thinking of adding to the CEP was to have an example yaml
config setup using the includes with the config grouped logically so people
have a reference example in the conf? Would this be a good idea?
On Fri, 18 Jul 2025 at 19:57, Johnny Miller
wrote:
> Hello 👋
>
>
> packaging and tooling (I assume someone, somewhere, has a "copy the yaml
> into the container" logic that doesnt know there may be multiple yamls).
>
>
>
> On 2025/07/18 17:57:03 Johnny Miller wrote:
> > Hello 👋
> >
> > We would like to propose CEP-5
pt from modular -> monolithic config shouldn't be too
>> complex. If that proved stable, integrating that into the build process and
>> even adding a checkstyle job target warning on non-classified configuration
>> parameters could tighten the whole thing up and give us a m
