Update: C/C NA Call for Presentations Deadline Extended to April 15th

Hi, I wanted to update that the Call for Presentations deadline was extended by two weeks to April 15th, 2024 for Community Over Code North America 2024. Find more information on this blog post: https://news.apache.org/foundation/entry/apache-software-foundation-opens-cfp-for-community-over-code-n

Re: [DISCUSS] Fixing coverage reports for jvm-dtest-upgrade

Thanks, looks good to me! > On Mar 19, 2024, at 10:19 AM, Abe Ratnofsky wrote: > > Here's where ClassLoader names were introduced in JDK9: > https://bugs.java.com/bugdatabase/view_bug?bug_id=6479237 > > And where Jacoco introduced support for the exclclassloader agent option: > https://github

Re: [DISCUSS] Fixing coverage reports for jvm-dtest-upgrade

Here's where ClassLoader names were introduced in JDK9: https://bugs.java.com/bugdatabase/view_bug?bug_id=6479237 And where Jacoco introduced support for the exclclassloader agent option: https://github.com/jacoco/jacoco/commit/b8ee4efe9c2ba93485fe5d9e25340113efc2390b My understanding is that n

Re: Default table compression defined in yaml.

We can not support both the "rule" that new settings have the new format, and the design goal that the CQL statement format be accepted. We came to a compromise. We introduced the new chunk_length parameter that requires a DataStorageSpec We reused the CQL chunk_length_in_kb parameter to accept th

Re: Default table compression defined in yaml.

Any new settings are expected to be added in the new format On Tue, 19 Mar 2024 at 5:52, Bowen Song via dev wrote: > I believe the `foobar_in_kb: 123` format in the cassandra.yaml file is > deprecated, and the new format is `foobar: 123KiB`. Is there a need to > introduce new settings entries wi

Re: Default table compression defined in yaml.

The earlier request was to be able to take the CQL statement and (with very little modification) use it in the YAML. While I agree that introducing the new setting to remove it later is a bit wonky, it is necessary to support the current CQL statement. Unless the CQL statement has changed already

Re: Default table compression defined in yaml.

I believe the `foobar_in_kb: 123` format in the cassandra.yaml file is deprecated, and the new format is `foobar: 123KiB`. Is there a need to introduce new settings entries with the deprecated format only to be removed at a later version? On 18/03/2024 14:39, Claude Warren, Jr via dev wrote: