This patch adds a test reproducing for the known issue #7963, where after adding a secondary-index to a table, queries might immediately start to use this index - even before it is built - and produce wrong results. The issue is still open and unfixed, so the new test is marked "xfail". Interestingly, even though Cassandra claims to have found and fixed a similar bug in 2015 (CASSANDRA-8505), this test also fails on Cassandra - trying a query right after CREATE INDEX and before it was fully built may cause the query to fail. Refs #7963 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#18993
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.