584f4e467e
There is a limited number of ways to obtain the schema of a table: 1) Use DESCRIBE TABLE in cqlsh 2) Find the schema definition in the code (for system tables) 3) Ask support/user to provide schema 4) Piece together the schema definition from the system tables Option (1) is the most convenient but requires access to live cluster. (2) is limited to system tables only. When investigating issues for customers, we have to rely on (3) and this often adds communication round-trips and delays. (4) requires knowledge of ScyllaDB internals and access to system tables. The new dump-schema commands provides a convenient way to obtain the schema of tables, given that there is access to either an sstable or the system tables. It can dump the schema of system tables without either. Closes scylladb/scylladb#26433
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.