3👍
Ah, the joys of trying to throw data across environments. The thing you’re being bitten by right now is called Pickle
and is the default serializer of django-redis
. What a serializer does in this case (in python) is the transformation of your data between python and redis so you can store it, regardless of the type, but more importantly so you can retrieve it with the type it came in.
The python side
Obviously, if you had infinite time and effort, you could rewrite pickle
in rust and you’d then be able to read this format. I’m pretty sure you have neither, and depending on the data you’re storing, you might not even want to do so.
Instead, what I’m going to suggest is to change the serializer from pickle
to json
. The description of what to change in the config is located at https://django-redis-cache.readthedocs.io/en/latest/advanced_configuration.html#pluggable-serializers , and in particular, I’m pretty sure the class name you want to use is django_redis.serializers.JSONSerializer
.
This comes with drawbacks. In particular, there will be some object types you will no longer be able to store on the python side, but if you do really intend to read data on the rust side, this should not concern you.
Sven Marnach mentioned in one of the comments that the serde-pickle
crate exists. I have not used it myself, but it does look promising and might save you a ton of interop work if it does function.
The rust side
To read stuff, now that every key is going to be json, you’ll be decoding types with either serde
or miniserde
. This should be pretty straightforward; do bear in mind that you will not get native types out of this; instead, you’ll get members of the serde::Value
enum (Boolean
, Number
, Object
, etc), which you will then have to filter through.
Edit your question to indicate what you are trying to store, and I’ll happily expand on how to do this on here!