-
Notifications
You must be signed in to change notification settings - Fork 539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How or where the follow relationship is stored ? #222
Comments
I am also stucked at same place and I am also not getting how serialized activities is stored in redis storage level. If you got it's workflow, can you please explain |
@The-Neo-Noir there is no follow storage included in the framework. The framework include APIs to create follows (and remove) between feeds (eg. let timeline X follow user Y) but where you store that is up to you. A common approach is to have a follow table to keep track of follow relationships. If you are familiar with Django:
@cosmologist10 the activity storage on Redis is pretty simple, they are stored in a K/V way Timelines don't include the full activity but only references |
Thanks for response. I have solved few dependencies issues, while running test cases. Let me know if I can contribute. |
@cosmologist10 that's great to hear! Best way is to create a PR with your changes |
@tbarbugli cool, I will create a PR by E.O.D and I have also solved docker issue of pinterest example. But even after solving all these issues, I am still not able to integrate this framework with my application. So, I am now trying to build feed modules from scratch. |
I have a question that when using redis to save notification feed (count, seen/unseen, read/unread) on ram, what happen if redis was restarted and how to init these value again? |
Redis is persistent, so it keeps data even if you restart it. |
Hi guys,
|
I am trying to understand this framework, but could not figure out how the follow relation is established and where that information is stored ( redis, or Cassandra)
The text was updated successfully, but these errors were encountered: