78d6ff6598
After migrating the view build status from system_distributed.view_build_status to system.view_build_status_v2, we set system_distributed.view_build_status to be a virtual table, such that reading from it is actually reading from the underlying new table. The reason for this is that we want to keep compatibility with the old table, since it exists also in Cassandra and it is used by various external tools to check the view build status. Making the table virtual makes the transition transparent for external users. The two tables are in different keyspaces and have different shard mapping. The v1 table is a distributed table with a normal shard mapping, and the v2 table is a local table using the null sharder. The virtual reader works by constructing a multishard reader which reads the rows from shard zero, and then filtering it to get only the rows owned by the current shard.
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.