OK, thanks all, we will go with 2), we will deprecate it in 5.0 and we remove
it the next major.
From: Jeff Jirsa
Sent: Monday, July 10, 2023 18:13
To: dev@cassandra.apache.org
Subject: Re: Removal of CloudstackSnitch
NetApp Security WARNING
+1
On Mon, Jul 10, 2023 at 8:42 AM Josh McKenzie wrote:
> 2) keep it there in 5.0 but mark it @Deprecated
>
> I'd say Deprecate, log warnings that it's not supported nor maintained and
> people to use it at their own risk, and that it's going to be removed.
>
> That is, assuming the
> 2) keep it there in 5.0 but mark it @Deprecated
I'd say Deprecate, log warnings that it's not supported nor maintained and
people to use it at their own risk, and that it's going to be removed.
That is, assuming the maintenance burden of it isn't high. I assume not since,
as Brandon said,
I agree with Ekaterina, but also want to point out that snitches are
pluggable, so whatever we do should be pretty safe. If someone
discovers after the removal that they need it, they can just plug it
back in.
Kind Regards,
Brandon
On Mon, Jul 10, 2023 at 8:54 AM Ekaterina Dimitrova
wrote:
>
>
: Monday, July 10, 2023 15:54
To: dev@cassandra.apache.org
Subject: Re: Removal of CloudstackSnitch
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.
Hi Stefan,
I think we should follow our
Hi Stefan,
I think we should follow our deprecation rules and deprecate it in 5.0,
potentially remove in 6.0. (Deprecate in one major, remove in the next
major)
Maybe the deprecation can come with a note on your findings for the users,
just in case someone somewhere uses it and did not follow the
Hi list,
I want to ask about the future of CloudstackSnitch.
This snitch was added 9 years ago (1). I contacted the original author of that
snitch, Pierre-Yves Ritschard, who is currently CEO of a company he coded that
snitch for.
In a nutshell, Pierre answered that he does not think this
