Madelyn Olson

I'm not sure it's really in the context here, but adding some standard fields that redis clients can send does seem generally like a good idea. Client name and version...

@roggervalf Sorry, we're aiming to finalize Redis 7 this and next week, so I'll circle back after that. You submitted a little bit too late to realistically try to merge...

@yossigo One use case that I've found very compelling, although IT vendor focused, is being able to notify customers that they are using an older version of a client that...

@yossigo I agree that we should also add the data to HELLO. Do we think that removes the need for the custom command though?

@yossigo I would expect end application developers to continue to use `CLIENT SETNAME`. The point of this command is just for clients to add additional metadata to the connection so...

> We want to maintain a counter that will give us the total number of kids. For a single shard, it is easy to implement, you create a function to...

@zuiderkwast It'll be a lot more complex than just allowing a client to forward a command to another node, since we still have cross shard linearizability issues. Let's say you...

@zuiderkwast I think that is what people use functions for, they expect it to be atomic. @oranagra I agree with most of the proposal, but I don't think we should...

I want to support something like `{:1235}foo` that maps the key into slot 1235. This will require a second iteration of the key routing, but I think it will be...

I also independently want the `{:1235}` syntax so the clients can deliberately place items in a slot, which we've seen with some AWS users. Some user has some extremely hot...