5bd503ad43
In issue #5320 we noticed that when we have a GSI with a hash key only (no range key) but the implementation's MV needs to add a clustering key for the original base key columns, the output of DescribeTable wrongly lists that exta "range key" - which isn't a real range key of the GSI. It turns out that the fact that the extra attribute is not a real GSI range key has another implication: It should not be allowed in KeyConditions or KeyConditionExpression - which should allow only real key columns of the GSI. This patch adds two reproducing tests for this issue (issue #2601), both pass on DynamoDB but xfail on Alternator. Signed-off-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.