[
https://issues.apache.org/jira/browse/CASSANDRA-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255671#comment-15255671
]
Christopher Batey commented on CASSANDRA-11634:
-----------------------------------------------
Thanks [~iamaleksey] I've added it at the cql layer where the timestamp is
either generated or taken from the client. This trace would have helped me
twice in the last week. Once for a clock skew issue for an insert, delete,
read, then still see the value as the delete went to a coordinator with its
clock behind and another issue where an app team were sure they weren't
specifying the timestamp but were due to a driver upgrade.
> Add write timestamp to trace
> ----------------------------
>
> Key: CASSANDRA-11634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11634
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability
> Reporter: Christopher Batey
> Assignee: Christopher Batey
> Priority: Minor
>
> Diagnosing issues with clock drift would be easier if trace had the mutation
> timestamp. I'll add a patch for this soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
