Paxos state tables are internal tables fully managed by Scylla and they shouldn't be exposed to the user nor they shouldn't be backed up. This commit hides those kind of tables from all listings and if such table is directly described with `DESC ks."tbl$paxos"`, the description is generated withing a comment and a note for the user is added. Fixes https://github.com/scylladb/scylladb/issues/28183 LWT on tablets and paxos state tables are present in 2025.4, so the patch should be backported to this version. - (cherry picked from commitf89a8c4ec4) - (cherry picked from commit9baaddb613) Parent PR: #28230 Closes scylladb/scylladb#28508 * github.com:scylladb/scylladb: test/cqlpy: add reproducer for hidden Paxos table being shown by DESC cql3/statements/describe_statement: hide paxos state tables
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.