K2V range watch and range diff #412

New Issue

Closed

opened 2022-11-10 11:24:44 +00:00 by lx · 1 comment

lx commented

2022-11-10 11:24:44 +00:00

Owner

It would be extremely usefull for Bay if we could query a K2V range for items that have changed since a previously returned result. This is probably not too hard to add, we just have to make sure that causality tokens are handled correctly. Would help a lot in reducing the data traffic between Aerogramme and Garage K2V.

It would be extremely usefull for Bay if we could query a K2V range for items that have changed since a previously returned result. This is probably not too hard to add, we just have to make sure that causality tokens are handled correctly. Would help a lot in reducing the data traffic between Aerogramme and Garage K2V.

lx added this to the v0.9 milestone 2022-11-10 11:24:44 +00:00

lx added the

label 2022-11-10 11:24:44 +00:00

lx self-assigned this 2022-12-11 17:44:27 +00:00

lx commented

2023-05-09 09:56:54 +00:00

Author

Owner

Fixed by #471

Fixed by #471

lx closed this issue

2023-05-09 09:56:56 +00:00

Sign in to join this conversation.

No Label

S3 Compatibility

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#412

No description provided.