Hi,
We're using 20.3 and would like to use a timestamp provided by an upstream
system during the put for updates to record column values.
Assuming the timestamp is trusted or can be identified as invalid by some
means,
are there any other issues to be aware of when using the timestamp form of the
put call?
The main reason we're interested in this is that it allows for out of order
processing of updates. i.e. an older update to a field arrives after an
already processed one. In this case, a "normal" read on the column value will
produce the correct column value.
-Doug
