Hi,
In the current codebase, JMXTimer exposes its attributes in inconsistent
time units. The percentiles, Mean and DurationUnit attributes are using
micros. But the Values and RecentValues are based on nanos, since the
underlying Timer collects the time values in nanos.
The inconsistency leads to
Java 11 support in Cassandra 3.11 would be fantastic. Is this something the
> Cassandra project will follow-up or is this a dead-end in favor of
> Cassandra 4.0, although Java 11 is marked as "experimental" there. Not sure
> what this means for production usage. 😊
>
Hi Thomas,
backporting to 3.1
+1
> On 24 Jun 2021, at 10:22, Sam Tunnicliffe wrote:
>
> +1
>
>> On 23 Jun 2021, at 22:31, Jeff Jirsa wrote:
>>
>> This would be my preference.
>>
>>
>> On Wed, Jun 23, 2021 at 2:22 PM Ben Bromhead wrote:
>>
>>> I'm also comfortable with a strict approach where we just list actual
>>> Ap
+1
> On 23 Jun 2021, at 22:31, Jeff Jirsa wrote:
>
> This would be my preference.
>
>
> On Wed, Jun 23, 2021 at 2:22 PM Ben Bromhead wrote:
>
>> I'm also comfortable with a strict approach where we just list actual
>> Apache Cassandra offerings, that also provides good solid clarity to users
