a659698c6d
With tablets, the test begun failing. The failure was correlated with the number of initial tablets, which when kept at default, equals 4 tablets per shard in release build and 2 tablets per shard in dev build. In this patch we split the test into two - one with a more data in the table to check the original purpose of this test - that Scan doesn't return the entire table in one page if "Limit" is missing. The other test reproduces issue #10327 - that when the table is small, Scan's page size isn't strictly limited to 1MB as it is in DynamoDB. Experimentally, 8000 KB of data (compared to 6000 KB before this patch) is enough when we have up to 4 initial tablets per shard (so 8 initial tablets on a two-shard node as we typically run in tests). Original patch by Piotr Szymaniak <piotr.szymaniak@scylladb.com> modified by Nadav Har'El <nyh@scylladb.com>
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.