Using JSON.SET with expiry

[jatinsandilya]

Using JSON.SET with expiry

[nitishm]

I don't think we want to support this. The Client is supposed to be dumb and should only support what the ReJSON spec provides.

With that said, a generic command to extend the Client is a good idea though. Even if it requires a rewrite we should support this. It is beneficial to support the fundamental features of the client which utilizing the ReJSON features.

[Shivam010]

I like the idea, and I think we have to use pipelined transactions, for something like this:

MULTI
JSON.SET foo ...
EXPIRE foo 60
EXEC

What do you propose?
@jats22 @nitishm

[Shivam010]

Also, if we can try for a generic method to run any command in an external transaction, that would solve the issue and would be much useful.

I don't know how we should do so in a generic way with different clients, but it's worth a discussion.

[jatinsandilya]

@Shivam010 I really think a generic method would be great! Let me put some thought into it and get back.

[Shivam010]

So, what do you propose? A transaction method or a expiry method...

…

On Mon, 23 Dec, 2019, 8:57 PM Nitish Malhotra, ***@***.***> wrote: I don't think we want to support this. The Client is supposed to be dumb and should only support what the ReJSON spec provides. With that said, a generic command to extend the Client is a good idea though. Even if it requires a rewrite we should support this. It is beneficial to support the fundamental features of the client which utilizing the ReJSON features. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub