This patch adds reproducer tests (still failing) for issue #20755, which is about missing validation of materialized view names: 1. Unlike table and keyspace names which are limited to 48 characters, we forgot to limit view name length, and an excessively long name can cause Scylla to shut down :-( 2. Unlike table and keyspace names which only allow alphanumeric characters, view names are missing this check and can include any characters. 3. Luckily, even though we are missing the alphanumeric check, we at least don't allow "/" in view names (if we allowed them, it could allow users to write in any directory in the filesystem!). But when this happens, we get an internal error instead of the expected errors. The first test also fails on Cassandra (it doesn't crash it, but leaves the table in a strange state), but the other two pass. Refs #20755 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#20761
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.