-
Notifications
You must be signed in to change notification settings - Fork 218
improve: PrimaryUpdateAndCacheUtils locks, naming and doc improvements #2799
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
Conversation
Signed-off-by: Attila Mészáros <[email protected]>
…CacheUtils Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
@xstefank @metacosm this is the next iteration of the primary caches. It provides an additional and I think preferred way to update the internal caches using update method with retryable optimistic locking. I think this should be the default what users should use. To be honest I'm a bit hesitant if we should provide the other approaches at this point. But would do this in a way that we merge this and in case I remove it in a subsequent PR - so we have history of alternatives. |
Replacement for this PR: #2800 |
Can we delete the branch? |
sure |
TODO