Currently server-side timestamps use a clock with millisecond precision. Timestamps have microsecond resolution, with lower bits used to serialize mutations originating from given client. Timestamps for column drops always use just the millisecond base. A column drop which is executed after an insert may thus be given lower timestamp than the insert, even when the two are serialized on the client side over same connection. Use microsecond precision to reduce chances of that event. This is supposed to fix sporadic failures of schema_test.py:TestSchema.drop_column_queries_test dtest. Message-Id: <1482343119-27698-1-git-send-email-tgrabiec@scylladb.com>
2.0 KiB
2.0 KiB