I am good with making >= 0 valid in both setters and config parsing, negatives
should error or produce defaults
> On Apr 4, 2022, at 10:45 AM, Caleb Rackliffe wrote:
>
> I'm for making >= 0 valid in both the setters and on startup. In the setters,
> I'm fine with either translating negative va
I'm for making >= 0 valid in both the setters and on startup. In the
setters, I'm fine with either translating negative values to the default
calculated value based on heap size or simply rejecting negative values. If
we really want to override that value, we had better have a really good
idea of w
I am cool with checking by default and disabling for tests that need it, it may
also make more sense to add an allow list so tests can explicitly say which
configs to ignore (though this sounds painful to implement).
> On Apr 4, 2022, at 9:11 AM, Jon Meredith wrote:
>
> I think checking the va
I think checking the validation rules as part of testing is important, but
making that a per-test concern for handling it may be frustrating.
What do you think about extending in-JVM with a method that provides the
previous config and version and expects the Instance implementation to
upgrade it,
Hi!
Do you have any more ideas for me?
Cordially,
Sébastien.
Le lun. 28 mars 2022 à 16:39, Sébastien Rebecchi
a écrit :
> Unfortunately, it is not working even with
> "enable_user_defined_functions_threads: false" in cassandra.yaml :/
> Is there any way to check the running configuration?
>
> Le
Hi everyone,
In In-jvm tests there is a flag Constants.KEY_DTEST_API_CONFIG_CHECK to
opt-in/out from config checks done in YamlConfigurationLoader#check().
The upgrade tests are currently set to ignore that check in order to work
around dealing with new properties in newer versions. What does this
Hi everyone,
While working on CASSANDRA-17431 to move the advanced Config parameters we
don't advertise in cassandra.yaml to the new types created in
CASSANDRA-15234, we ran into some concerns around
native_transport_max_concurrent_requests_in_bytes
and native_transport_max_concurrent_requests_in_b
We went last week without a Build Lead. We have one for this week, but we
are looking for volunteers for next week and the weeks ahead.
This is an important activity to get us to green - once we are green it
opens new possibilities for us.
So please sign up :-)
On Fri, 25 Mar 2022 at 19:50, And
> * Freeze cassandra-4.1 on may 1st
>
A feature freeze on the release branch is always implied.
And repeating, because it bugs me (and I just need to air it): we're
talking about this because we have not achieved a stable trunk this dev
cycle.
The 4.0 branch has remained very close, but trunk n
I created a company page for Apache Cassandra with the same admin as the
group.
I will update the page over the coming days to give it a nicer look. :-)
Le mer. 30 mars 2022 à 23:46, Patrick McFadin a écrit :
> Oh and +1 to the idea of making Apache Cassandra a company on LinkedIn.
> Same energy
I just did the same for cassandra-accord, I guess some config was lost in the
upgrade
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-23074
From: Mick Semb Wever
Date: Monday, 4 April 2022 at 08:55
To: dev@cassandra.apache.org
Subject: Re: [GitHub] [cassandra-website] ossarga comme
these notifications should be going to pr@
have created https://issues.apache.org/jira/browse/INFRA-23073
On Mon, 4 Apr 2022 at 03:09, GitBox wrote:
>
> ossarga commented on code in PR #121:
> URL:
> https://github.com/apache/cassandra-website/pull/121#discussion_r841307662
>
>
> ##
> s
belliottsmith commented on code in PR #2:
URL: https://github.com/apache/cassandra-accord/pull/2#discussion_r841458215
##
accord-core/src/main/java/accord/local/CommandStore.java:
##
@@ -228,7 +228,7 @@ public void processBlocking(Consumer
consumer)
}
catch (I
13 matches
Mail list logo
