Wanted to add some that I remembered:
* https://issues.apache.org/jira/browse/CASSANDRA-12811 - data
resurrection, but was marked as normal because was discovered with a test.
Should've marked it as critical.
* https://issues.apache.org/jira/browse/CASSANDRA-12956 - data loss
(commit log isn't
"ML is plaintext bro" - thanks Mick. ಠ_ಠ
Since we're stuck in the late 90's, here's some links to a gsheet:
Defects by month:
https://docs.google.com/spreadsheets/d/1Qt8lLIiqVvK7mlSML7zsmXdAc-LsvktFW5RXJDRtN8k/edit#gid=1584867240
Defects by component:
https://docs.google.com/spreadsheets/d/1Qt8lL
4.0 release that users can trust and adopt quickly.
– Scott
From: Joshua McKenzie
Sent: Thursday, May 7, 2020 9:31 AM
Cc: dev@cassandra.apache.org
Subject: Re: List of serious issues fixed in 3.0.x
Hearing the images got killed by the web server. Trying from
Hearing the images got killed by the web server. Trying from gmail (sorry
for spam). Time to see if it's the apache smtp server or the list culling
images:
---
I did a little analysis on this data (any defect marked with fixversion 4.0
that rose to the level
I did a little analysis on this data (any defect marked with fixversion 4.0
that rose to the level of critical in terms of availability, correctness,
or corruption/loss) and charted some things the rest of the project
community might find interesting:
1: Critical (availability, correctness, corrup
Hi Sankalp,
Thanks for bringing this up. At the very minimum, I hope we have regression
tests for the specific issues we have fixed.
I personally think, the project should focus on building a comprehensive test
suite. However, some of these issues can only be detected at scale. We need
users t
Hi,
I want to share some of the serious issues that were found and fixed in
3.0.x. I have created this list from JIRA to help us identify areas for
validating 4.0. This will also give an insight to the dev community.
Let us know if anyone has suggestions on how to better use this data in
vali
