Scylla refuses the timestamp format "2014-01-01 12:15:45.0000000Z" that has 6 digits of precision for the fractional second, and only allows 3 digits of precision. This restriction makes sense - after all CQL timestamp columns (note - this is NOT "using timestamp"!) only have millisecond precision. Nevertheless, Cassandra does not have this restriction and does allow these over-precise timestamps. In this patch we add a test that demonstrates this difference. Curiously, in the past Scylla *generated* this forbidden timestamp format when outputting the timestamp to a string (e.g. toJson()), which it then couldn't read back! This was issue #16575. Today Scylla no longer generates this forbidden timestamp format. Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#16576
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cql-pytest - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.