Thanks Erick. Good thinking on getting the Infra team involved.
On 11/02/2022 23:05, Erick Ramirez wrote:
Thanks for bringing it up. I've been meaning to look into this. It got
annoying enough for me today that I got ASF Infra team to investigate
and the offending address has now been removed
Note taken, I had to document only in 4.0.x that those are placeholder. I
just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
patch soon
On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa wrote:
> We don't HAVE TO remove the Config.java entry - we can mark it as
> deprecated and
Agreed, I've opened CASSANDRA-17376 to handle this.
On Fri, Feb 11, 2022 at 4:44 PM Jeff Jirsa wrote:
>
> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated
> and ignored and remove it in a future version (and you could update
> Config.java to log a message about
Thanks for bringing it up. I've been meaning to look into this. It got
annoying enough for me today that I got ASF Infra team to investigate and
the offending address has now been removed from the list (
https://issues.apache.org/jira/browse/INFRA-22879). Cheers!
We don't HAVE TO remove the Config.java entry - we can mark it as
deprecated and ignored and remove it in a future version (and you could
update Config.java to log a message about having a deprecated config
option). It's a much better operator experience: log for a major version,
then remove in
This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
fix a bug that gives impression those work. Confirmed with Benedict on the
ticket.
I agree I absolutely had to document it better, a ticket for documentation
was opened but it slipped from my mind with this emergency
(moved dev@ to BCC)
> It looks like the otc_coalescing_strategy config key is no longer
> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
> anywhere in CHANGES.txt or NEWS.txt.
>
James, you're right -- it was removed by CASSANDRA-17132
Accidentally dropped dev@, so adding back in the dev list, with the hopes
that someone on the dev list helps address this.
On Fri, Feb 11, 2022 at 2:22 PM Jeff Jirsa wrote:
> That looks like https://issues.apache.org/jira/browse/CASSANDRA-17132 +
>
That looks like https://issues.apache.org/jira/browse/CASSANDRA-17132 +
https://github.com/apache/cassandra/commit/b6f61e850c8cfb1f0763e0f15721cde8893814b5
I suspect this needs to be reverted, at least in 4.0.x, and it definitely
deserved a NEWS.txt entry (and ideally some period of
It looks like the otc_coalescing_strategy config key is no longer supported
in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in
CHANGES.txt or NEWS.txt.
Attempting to upgrade a test cluster from 4.0.1 to 4.0.2 failed with *"Invalid
yaml. Please remove properties
Severity: high
Description:
When running Apache Cassandra with the following configuration:
enable_user_defined_functions: true
enable_scripted_user_defined_functions: true
enable_user_defined_functions_threads: false
it is possible for an attacker to execute arbitrary code on the host. The
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.2.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.12.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.26.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
14 matches
Mail list logo