Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Later
-
None
-
None
-
None
Description
In a context where we are doing aggregation/combination of multiple values for a given key it may be useful to iterate over the values associated with that key in the order in which the mutations were applied (FIFO), instead of the FILO order that seems to occur when using TimeType.LOGICAL.
I encountered when implemeting a checkAndPut operation that would ensure that the previous value was expected before putting a new value. In this case, if the previous value was not as expected, the mutation would be ignored.
Perhaps it is useful in a general case?
Attachments
Attachments
Issue Links
- links to