-
Notifications
You must be signed in to change notification settings - Fork 27
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
Conflict Resolution Strategy #23
Comments
Hey @abakermi, this is a good point. Feel free to open a PR that addresses this. Make sure to also include any proposed fixes in the sqlite data connector. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
RedisService
currently lacks a mechanism to handle conflicts that arise when concurrent operations attempt to update the same key with different values. We can resolve that based on timestamp ,the approach involves modifying the set method to include a timestamp and compare it with the timestamp of the current data in Redis. If a conflict is detected (the existing data is newer), the update will be rejected. This enhancement is crucial for maintaining data integrity in scenarios with concurrent data operations.The text was updated successfully, but these errors were encountered: