I second Brandon. There is a group of people who expect to ssh into a node and
then be able to run the "right" cqlsh instead of dealing with different cqlsh
versions on their workstation/laptop...
German
From: Brandon Williams
Sent: Friday, August 11, 2023 7:29
+1
The rationale for deprecating/removing this library is not just that
it is obsolete and doesn't get updates. In fact, when the
metrics-reporter-config [1] was added the dropwizard metrics library
(formerly com.yammer.metrics [2]) didn't support exporting metrics to
files like csv, so it made se
+1
> On Aug 11, 2023, at 8:10 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Fri, Aug 11, 2023 at 8:08 AM Ekaterina Dimitrova
>> wrote:
>>
>>
>> “ The rationale for this proposed deprecation is that the upcoming 5.0
>> release is a good time to evaluate dependencie
On Fri, Aug 11, 2023 at 2:13 AM Miklosovic, Stefan
wrote:
>
> If we had an official PIP package, I can imagine that we would not ship CQLSH
> in RPM at all (maybe not in DEB either?) so we would decouple this. A PIP
> package is installable almost anywhere (if it is Python 3, that is the way
>
Hi,
While doing some local testing, I noticed that my /tmp drive completely
filled with test artifact files (e.g. data directories, logs, commit logs,
etc). Mick pointed out that we do attempt to do some "find" based cleanup
in CI (
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl
+1
Kind Regards,
Brandon
On Fri, Aug 11, 2023 at 8:08 AM Ekaterina Dimitrova
wrote:
>
>
> “ The rationale for this proposed deprecation is that the upcoming 5.0
> release is a good time to evaluate dependencies that are no longer receiving
> updates and will become risks in the future.”
>
> Th
“ The rationale for this proposed deprecation is that the upcoming 5.0
release is a good time to evaluate dependencies that are no longer
receiving updates and will become risks in the future.”
Thank you for raising it, I support your proposal for deprecation
On Fri, 11 Aug 2023 at 8:55, Abe Ratn
Hey folks,
Opening a thread to get input on a proposed dependency deprecation in 5.0:
metrics-reporter-config has been archived for 3 years and not updated in nearly
6 years.
This project has a minor security issue with its usage of unsafe YAML loading
via snakeyaml’s unprotected Constructor:
One nice benefit of a CQLSH PIP package which was omitted in this discussion is
that it is "Python-version-agnostic". What I mean by that is that the way how
we currently package CQLSH in RPM is that the container it is produced in is
using Python 3.6 so the produced RPM will run, believe or not
