dfaed80f55
This PR introduces a new `comparable_bytes` class to add byte-comparable format support for all the [native cql3 data types](https://opensource.docs.scylladb.com/stable/cql/types.html#native-types) except `counter` type as that is not comparable. The byte-comparable format is a pre-requisite for implementing the trie based index format for our sstables(https://github.com/scylladb/scylladb/issues/19191). This implementation adheres to the byte-comparable format specification in https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/utils/bytecomparable/ByteComparable.md Note that support for composite data types like lists, maps, and sets has not been implemented yet and will be made available in a separate PR. Refs https://github.com/scylladb/scylladb/issues/19407 New feature - backport not required. Closes scylladb/scylladb#23541 * github.com:scylladb/scylladb: types/comparable_bytes: add testcase to verify compatibility with cassandra types/comparable_bytes: support variable-length natively byte-ordered data types types/comparable_bytes: support decimal cql3 types types/comparable_bytes: introduce count_digits() method types/comparable_bytes: support uuid and timeuuid cql3 types types/comparable_bytes: support varint cql3 type types/comparable_bytes: support skipping sign byte write in decode_signed_long_type types/comparable_bytes: introduce encode/decode_varint_length types/comparable_bytes: support float and double cql3 types types/comparable_bytes: support date, time and timestamp cql3 types types/comparable_bytes: support bigint cql3 type types/comparable_bytes: support fixed length signed integers types/comparable_bytes: support boolean cql3 type types: introduce comparable_bytes class bytes_ostream: overload write() to support writing from FragmentedView docs: fix minor typo in docs/dev/cql3-type-mapping.md
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.