bd6eeb4730
This patch doesn't yet change how schema merging works but it prepares the ground for it by simplifying the code and separating merging logic into its own unit. It consists of: - minor cleanups of unused code - moving code into separate file - simplifying merge_keyspaces code More detailed explanation in per commit messages. Relates scylladb/scylladb#19153 Closes scylladb/scylladb#19687 * github.com:scylladb/scylladb: db: schema_applier: simplify merge_keyspaces function db: schema_applier: remove unnecessary read in merge_keyspaces db: schema_tables: move scylla specific code into create keyspace function db: move schema merging code into a separate unit db: schema_tables: export some schema management functions replica: remove unused table_selector forward declaration db: remove unused flush arg from do_merge_schema func db: remove unused read_arg_values function
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.