[
https://issues.apache.org/jira/browse/CASSANDRA-8679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290975#comment-14290975
]
Nils Kilden-Pedersen commented on CASSANDRA-8679:
-------------------------------------------------
It's not trivial, because we have multiple clients writing and cannot rely the
inevitable time skew. Note, I need the time to be always increasing (or equal)
in the order they are written. This cannot be guaranteed with client side
timestamping. Also, I know that server-side timestamping will only work per
node, but this is acceptable, since I don't require absolute increasing time,
only relative per the key I'm using, which is always on the same node.
> Successful LWT INSERT should return any server generated values
> ---------------------------------------------------------------
>
> Key: CASSANDRA-8679
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8679
> Project: Cassandra
> Issue Type: Wish
> Reporter: Nils Kilden-Pedersen
>
> A failed LWT INSERT returns the row that prevented insertion, along with
> `[applied]` boolean value. A successful LWT INSERT only returns `[applied]`.
> It would be helpful to also return any other server generated values, e.g.
> `NOW()` as `[now]` (or whatever).
> There is currently no way to know what exactly was inserted without
> re-querying the row, which is horrible for write-throughput.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
