Re: [EXTERNAL] Re: [DISCUSSION] CEP-38: CQL Management API

2023-11-23 Thread Maxim Muzafarov
Hi, I've made a few updates to the design document to reflect the comments we've received. However, the admin port (service port) has not been removed from the document yet, but I think we can do that since it's not necessary for the initial implementation. I also think that the k8ssandra-manageme

Re: [EXTERNAL] Re: [DISCUSSION] CEP-38: CQL Management API

2023-11-20 Thread Jake Luciani
Hi, I originally worked on the management API sidecar mentioned above. I'm excited to see there's renewed interest in the cql for ops concept. Though it currently uses an agent to inject the local socket for cql (so it can be used by older versions of Apache Cassandra), Similar logic like the man

Re: [EXTERNAL] Re: [DISCUSSION] CEP-38: CQL Management API

2023-11-20 Thread German Eichberger via dev
Hi, >From a cloud provider perspective we expose the storage port to customers for >Hybrid scenarios (e.g. fusing on-prem Cassandra with in-cloud Cassandra) so >would prefer an extra port or a socket. Thanks, German From: Dinesh Joshi Sent: Friday, November 17,