You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: