Am I understanding it correctly that tests you are talking about are only required in case we make ACCP to be default provider?
I can live with not making it default and still deliver it if tests are not required. I do not think that these kind of tests were required couple mails ago when opt-in was on the table. While I tend to agree with people here who seem to consider testing this scenario to be unnecessary exercise, I am afraid that I will not be able to deliver that as testing something like this is quite complicated matter. There is a lot of aspects which could be tested I can not even enumerate right now ... so I try to meet you somewhere in the middle. ________________________________________ From: Mick Semb Wever <m...@apache.org> Sent: Wednesday, July 26, 2023 17:34 To: dev@cassandra.apache.org Subject: Re: [DISCUSS] Using ACCP or tc-native by default NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. Can you say more about the shape of your concern? Integration testing where some nodes are running JCE and others accp, and various configurations that are and are not accp compatible/native. I'm not referring to (re-) unit testing accp or jce themselves, or matrix testing over them, but our commitment to always-on upgrades against all possible configurations that integrate. We've history with config changes breaking upgrades, for as simple as they are.
