Hi, I was playing around with a go redis package and saw support for client side caching.
https://redis.io/docs/manual/client-side-caching/
When running it with dragonfly I got the following error
panic: Unknown subcommand or wrong number of arguments for 'TRACKING'. Try CLIENT HELP.: ClientOption.DisableCache must be true for redis not supporting client-side caching or not supporting RESP3
via the command reference i see that the CLIENT Tracking command is not yet supported, will there be any ETA for when it is availiable?
hi client tracking was just merged into our main branch, so it will be officially available in the next release
meanwhile, you could try our weekly built container image
our weekly builds can be pulled via
docker pull ghcr.io/dragonflydb/dragonfly-weekly
currently we only support using client tracking under resp3, so make sure you do hello 3 or redis-cli -3
before issuing client tracking on
thanks for the fast response, ill give it a shot!
let us know if there is any question. And please note we currently only support client tracking on and off without other command options
just tried it out, tracking is not an issue anymore but the CLIENT CACHING command which is also not yet supported.
I’ve just disabled client side caching in the library and will look forward when client side caching is supported in dragonfly
correct, client caching is currently not supported. Could you elaborate your use case? this would help to us prioritize different features
this is not a priority to me, I would’ve wanted to use client caching in order to increase throughput
i see, just wondered do you use this for php caching or something else? for php caching there are frameworks that implement independent client caching using our client tracking, so you dont need to use client caching command
I use it for something else,
the go library I use (https://github.com/redis/rueidis) sends the following commands:
CLIENT CACHING YES
PTTL k
GET k
got it, thanks for the information!