36347c3ce9
Cassandra changed their system tables in 3.0. We migrated to the new system table layout in 2017, in ScyllaDB 2.0. System tables introduced in Cassandra 3.0, as well as the 3.0 variant of pre-existing system tables were added to the db::system_table::v3 namespace. We ended up adding some new ScyllaDB-only system tables to this namespace as well. As the dust settled, most of the v3 system tables ended up being either simple aliases to non-v3 tables, or new tables. Either way, the codebase uses just one variant of each table for a long time now the v3:: distinction is pointless. Remove the v3 namespace and unify the table listing under the top-level db::system_keyspace scope. Code cleanup, no backport Closes scylladb/scylladb#28146 * github.com:scylladb/scylladb: db/system_keyspace: move remining tables out of v3 keyspace db/system_keyspace: relocate truncated() and commitlog_cleanups() db/system_keyspace: drop v3::local() db/system_keyspace: remove duplicate table names from v3
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++ cqlpy - 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.