mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-29 19:21:01 +00:00
9e67bd5aac
"This series introduces partial support for range deletions. This allows deletion operations such as delete from cf where p=1 and c > 0 and c <= 3. This series only adds support for single-column range restrictions. We enforce that both range bounds be specified, because we can't represent infinite bounds in the current sstable format. Such bounds are represented as a prefix with no components, with the bound_kind informing whether they are a bottom of top bound. We're currently unable to serialize an infinite bound in such a way that it would be correctly interpreted by Cassandra 2.2.x. A serialized bound is a composite with a (<length><value><EOC>)+ format. While we could technically represent the bottom bound, the top bound, if written as a single component with 0 bytes in size and some EOC, would always sort before other values. The same would happen if represented as an empty (no components) composite, because in Cassandra 2.2.x those always have EOC = NONE. This limitation should stay in place until we can properly represent range tombstones in the storage format." * 'range-deletions/v2' of https://github.com/duarten/scylla: mutation: Set cell using clustering_key_prefix mutation_partition: Harmonize apply_delete overloads prefix_compound_view_wrapper: Add is_full and is_empty functions tests/cql_query_test: Add range deletion tests cql3: Partially support ranged deletions single_column_primary_key_restrictions: Implement has_bound() modification_statement: Use statement_restrictions for where clause statement_restrictions: Expose primary key restrictions to_string: Add missing include