and testing is desperately needed.
More detailed feedback below.
On Fri, 24 May 2024 at 16:08, Brandon Williams
mailto:dri...@gmail.com>> wrote:
On Thu, May 23, 2024 at 5:51 PM Fleming, Jackson via dev
mailto:dev@cassandra.apache.org>> wrote:
> Primarily this would be moving fro
Hi All,
Instaclustr is considering updating the Jenkins agents that we’ve donated to
the project
(https://github.com/apache/cassandra-builds/blob/trunk/ASF-jenkins-agents.md) –
we’d like to update the instance types of these from the current M4 2 X-Large
sizes to M7G 2 X-Large.
Primarily
Sorry centered not “cantered”
From: Fleming, Jackson
Date: Wednesday, 24 January 2024 at 6:29 pm
To: dev@cassandra.apache.org
Subject: Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available
Silly question but there was just a 4.0.12 release, should users avoid adopting
Silly question but there was just a 4.0.12 release, should users avoid adopting
that or is the concern more cantered around CI and testing? Does a 4.0.13 need
to be considered?
Regards,
Jackson
From: Berenguer Blasi
Date: Wednesday, 24 January 2024 at 5:01 pm
To: dev@cassandra.apache.org
We use Nodetool in scripts sparsely, in my opinion trying to programmatically
parse the human readable output should be avoided as much as possible, it’s
usually leads to implementations that are brittle.
I certainly agree you don’t want to make these kinds of changes in 3.11 or 4.x
(and I
We run ACCP in production on 1000s of nodes across Cassandra 3.11 and 4 with
great results.
Would love to see it baked into Cassandra.
Jackson
From: David Capwell
Date: Friday, 23 June 2023 at 9:22 am
To: dev
Subject: Re: [DISCUSS] Using ACCP or tc-native by default
NetApp Security WARNING:
I agree that the log sent back to the user is perhaps too verbose for an audit
log, Jeff’s log format is nice in that regard, due to a clear pattern (nice for
log parsers) with a clear distinct reason for failure that has enough details
for an auditor to understand what happened, though it gets
I agree that any password change (or attempted change) would be very important
audit data that would need to be captured, I don’t think that auditors would
necessarily need to know the reason for rejection for a validator? Maybe I’ve
just worked within less strict auditing requirements though.
Password Meter - This is an interesting use case, password meters work really
well when users are using a visual aid (like a website sign up page). I’d be
concerned by just limiting the complexity that we would require to a single
number, when a user attempts to create or update a password
