cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12767) Cassandra Java Driver 3.1.0 Client-Side timestamp generation issue
Date Mon, 10 Oct 2016 16:17:20 GMT


Jeremy Hanna commented on CASSANDRA-12767:

{{ifnotexists}} uses a lightweight transaction within the cluster to provide some guarantees.
 You can't do this with a client-side timestamp.  So for anything that doesn't require a server-side
timestamp, it uses a client-side timestamp.

Generally though, it's best to do clock syncing (e.g. ntp) within the cluster and on client
machines, so in practice it shouldn't matter very much either way.

> Cassandra Java Driver 3.1.0 Client-Side timestamp generation issue
> ------------------------------------------------------------------
>                 Key: CASSANDRA-12767
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.1.15
> Cassandra Java Driver 3.1.0
>            Reporter: Ye Liang
>            Priority: Minor
> I use cassandra driver java to do some insert operation.I notice that Cassandra Java
Driver use client-side timestamp as default.
> I make my client server one hour ahead than my cassandra server,then i insert some record
to an exist table and use sstable2json tool to check my record ' s timestamp.
> i find out that if i insert a record with ifnotexist,the record's timestamp used server-side
timestamp,otherwise it use client-side timestamp.
> I think this is a very strange result.

This message was sent by Atlassian JIRA

View raw message