Re: Proposing an Apache Cassandra Management process

2018-04-18 Thread Dinesh Joshi
Thank you all for the feedback. Nate made a Google doc with the proposal in it and is linked off of the ticket. I will try to flesh it out as I gather your input. Dinesh On Wednesday, April 18, 2018, 5:12:49 PM PDT, kurt greaves wrote: For anyone looking Dinesh made a ticket already:

Re: Proposing an Apache Cassandra Management process

2018-04-18 Thread kurt greaves
For anyone looking Dinesh made a ticket already: CASSANDRA-14395 On 18 April 2018 at 18:14, Vinay Chella wrote: > This is a good initiative. We have advocated for and run a sidecar for the > past 5+ years, and we've learned and improved it

Re: Evolving the client protocol

2018-04-18 Thread Jonathan Haddad
Avi, if this is something that matters to you, you're more than welcome to submit a patch to both this project and to the different drivers. Getting the first 2 optimizations into 4.0 would be nice, I'm sure someone would be happy to work with you on it. The third, I can't see why we'd need that

Re: Evolving the client protocol

2018-04-18 Thread sankalp kohli
Do we have driver authors who wish to support both projects? On Wed, Apr 18, 2018 at 9:25 AM, Jeff Jirsa wrote: > Removed other lists (please don't cross post) > > > > > > On Wed, Apr 18, 2018 at 3:47 AM, Avi Kivity wrote: > > > Hello Cassandra developers, > > > > > > We're starting to see clie

Re: Proposing an Apache Cassandra Management process

2018-04-18 Thread Vinay Chella
This is a good initiative. We have advocated for and run a sidecar for the past 5+ years, and we've learned and improved it a lot. We look forward to moving features from Priam (such as backup, HTTP -> JMX, etc) incrementally to this sidecar as they make sense. Thanks, Vinay Chella On Fri, Apr 1

Re: Evolving the client protocol

2018-04-18 Thread Glauber Costa
BTW, Folks from Cassandra apparently didn'tr eceive this message. On Wed, Apr 18, 2018 at 6:47 AM, Avi Kivity wrote: > Hello Cassandra developers, > > > We're starting to see client protocol limitations impact performance, and > so we'd like to evolve the protocol to remove the limitations. In

Re: Evolving the client protocol

2018-04-18 Thread Jeff Jirsa
Removed other lists (please don't cross post) On Wed, Apr 18, 2018 at 3:47 AM, Avi Kivity wrote: > Hello Cassandra developers, > > > We're starting to see client protocol limitations impact performance, and > so we'd like to evolve the protocol to remove the limitations. In order to > avoid

Evolving the client protocol

2018-04-18 Thread Avi Kivity
Hello Cassandra developers, We're starting to see client protocol limitations impact performance, and so we'd like to evolve the protocol to remove the limitations. In order to avoid fragmenting the driver ecosystem and reduce work duplication for driver authors, we'd like to avoid forking th