a8bc90a375
This series fixes two related inconsistencies around secondary-index names. 1. `DESCRIBE INDEX ... WITH INTERNALS` returned the backing materialized-view name in the `name` column instead of the logical index name. 2. The snapshot REST API accepted backing table names for MV-backed secondary indexes, but not the logical index names exposed to users. The snapshot side now resolves logical secondary-index names to backing table names where applicable, reports logical index names in snapshot details, rejects vector index names with HTTP 400, and keeps multi-keyspace DELETE atomic by resolving all keyspaces before deleting anything. The tests were also extended accordingly, and the snapshot test helper was fixed to clean up multi-table snapshots using one DELETE per table. Fixes: SCYLLADB-1122 Minor bugfix, no need to backport. Closes scylladb/scylladb#29083 * github.com:scylladb/scylladb: cql3: fix DESCRIBE INDEX WITH INTERNALS name test: add snapshot REST API tests for logical index names test: fix snapshot cleanup helper api: clarify snapshot REST parameter descriptions api: surface no_such_column_family as HTTP 400 db: fix clear_snapshot() atomicity and use C++23 lambda form db: normalize index names in get_snapshot_details() db: add resolve_table_name() to snapshot_ctl
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.