Please forget about this email,
there was a long forgotten client running somwhere in our data center that
caused this problem.
Von: Daniel Stucky [mailto:daniel.stu...@empolis.com]
Gesendet: Montag, 5. Oktober 2015 09:02
An: user@cassandra.apache.org
Betreff: Strange behavior of timestamp
Hi all,
we have a very simple cassandra table that contains just a single row. We have
a 3-machine cluster using Cassandra 2.1.8, cqlsh 5.0.1.
I do the following:
CREATE TABLE IF NOT EXISTS scheduler_config (name text, suspended boolean,
modified_ts timestamp, last_scheduled_start_ts timestam
