-
Notifications
You must be signed in to change notification settings - Fork 177
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
chore(sync-service): Decouple Timeline from ShapeCache #1846
chore(sync-service): Decouple Timeline from ShapeCache #1846
Conversation
1857bff
to
edbbccd
Compare
7ec3345
to
ae60ac5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I think we can actually get rid of persistent_kv
altogether and make Timeline
write directly to a single file (it was used for ShapeStatus
before but I've removed that, so it is now only used by Timeline
) - we can do that in a separate PR
edbbccd
to
c14c6fe
Compare
This change reduces coupling between Timeline and ShapeCache modules, resulting in easier comprehension and maintenance of this small part of the code. ConnectionManager serves as the supervisor of the connection startup procedure and that's where we keep the knowledge about how a change in PG timeline affects the shape cache. As a bonus, we don't have to first start all shape consumers just to bring them all down afterwards, as we've been doing up until this change.
ae60ac5
to
8381a60
Compare
Merged into |
PR chain: #1842 ← #1841 ← #1845 ← #1846 ← #1862
See individual commits to get a better idea of what this PR achieves.