Is there a technical limitation that would prevent a range write that functions the same way as a range tombstone, other than probably needing a version bump of the storage format?
On Tue, May 14, 2024 at 12:03 AM Benjamin Lerer <ble...@apache.org> wrote: > Range restrictions (>, >=, =<, < and BETWEEN) do not work on UPDATEs. They > do work on DELETE because under the hood C* they get translated into range > tombstones. > > Le mar. 14 mai 2024 à 02:44, David Capwell <dcapw...@apple.com> a écrit : > >> I would also include in UPDATE… but yeah, <3 BETWEEN and welcome this >> work. >> >> On May 13, 2024, at 7:40 AM, Patrick McFadin <pmcfa...@gmail.com> wrote: >> >> This is a great feature addition to CQL! I get asked about it from time >> to time but then people figure out a workaround. It will be great to just >> have it available. >> >> And right on Simon! I think the only project I had as a high school >> senior was figuring out how many parties I could go to and still maintain a >> passing grade. Thanks for your work here. >> >> Patrick >> >> On Mon, May 13, 2024 at 1:35 AM Benjamin Lerer <ble...@apache.org> wrote: >> >>> Hi everybody, >>> >>> Just raising awareness that Simon is working on adding support for the >>> BETWEEN operator in WHERE clauses (SELECT and DELETE) in CASSANDRA-19604. >>> We plan to add support for it in conditions in a separate patch. >>> >>> The patch is available. >>> >>> As a side note, Simon chose to do his highschool senior project >>> contributing to Apache Cassandra. This patch is his first contribution for >>> his senior project (his second feature contribution to Apache Cassandra). >>> >>> >>> >>
