search

redis / redis-om-python

Object mapping, and more, for Redis and Python
MIT License
1.09k stars 108 forks source link

Is Redis OM stable? I mean is it production ready? #461

Open ok-pennywise opened 1 year ago

XChikuX commented 1 year ago

It most definitely is not. This is a preview repository, I've run into multiple issues which will hopefully be ironed out soon.

dinkopehar commented 1 year ago

@XChikuX Can you share issues that you had ? I understand that this is still in preview, but I'm not sure how much this is usable. What I'm looking for is that models are stable enough for work. Not sure what other problems are there...

XChikuX commented 1 year ago

@dinko-pehar Stay clear of cluster workloads.

I've found that, it is mostly stable for a single instance of redis. Both sync and async are usable.

Make sure you only embed EmbeddedJsonModel in a JsonModel and not a HashModel as this causes issues. Ensure you include Migrator().run() in the correct locations. This isn't documented well at all. I just run it in random places and things seem to work.

Works fine other than the above cases. This repo hasn't been updated in a while though. Not sure what their long term plan for this is.

EDIT: Also avoid multiple layers of JSON for now. A depth of one works fine.

chgiesse commented 11 months ago

@dinko-pehar Stay clear of cluster workloads.

I've found that, it is mostly stable for a single instance of redis. Both sync and async are usable.

Make sure you only embed EmbeddedJsonModel in a JsonModel and not a HashModel as this causes issues. Ensure you include Migrator().run() in the correct locations. This isn't documented well at all. I just run it in random places and things seem to work.

Works fine other than the above cases. This repo hasn't been updated in a while though. Not sure what their long term plan for this is.

EDIT: Also avoid multiple layers of JSON for now. A depth of one works fine.

I am running into the same issues with the migrator! Could you see any improvements ?