f3eade2f62
Drop the AGPL license in favor of a source-available license. See the blog post [1] for details. [1] https://www.scylladb.com/2024/12/18/why-were-moving-to-a-source-available-license/
71 lines
3.5 KiB
Python
71 lines
3.5 KiB
Python
# Copyright 2021-present ScyllaDB
|
|
#
|
|
# SPDX-License-Identifier: LicenseRef-ScyllaDB-Source-Available-1.0
|
|
|
|
#############################################################################
|
|
# Various tests for Scylla's ttl feature - USING TTL and DEFAULT_TIME_TO_LIVE
|
|
#############################################################################
|
|
|
|
from .util import new_test_table, unique_key_int
|
|
from cassandra.query import UNSET_VALUE
|
|
import pytest
|
|
import time
|
|
|
|
# Fixture with a table with a default TTL set to 1, so new data would be
|
|
# inserted by default with TTL of 1.
|
|
@pytest.fixture(scope="module")
|
|
def table_ttl_1(cql, test_keyspace):
|
|
with new_test_table(cql, test_keyspace, 'p int primary key, v int', 'with default_time_to_live = 1') as table:
|
|
yield table
|
|
|
|
@pytest.fixture(scope="module")
|
|
def table_ttl_100(cql, test_keyspace):
|
|
with new_test_table(cql, test_keyspace, 'p int primary key, v int', 'with default_time_to_live = 100') as table:
|
|
yield table
|
|
|
|
|
|
# Basic test that data inserted *without* an explicit ttl into a table with
|
|
# default TTL inherits this TTL, but an explicit TTL overrides it.
|
|
def test_basic_default_ttl(cql, table_ttl_1):
|
|
p1 = unique_key_int()
|
|
p2 = unique_key_int()
|
|
cql.execute(f'INSERT INTO {table_ttl_1} (p, v) VALUES ({p1}, 1) USING TTL 1000')
|
|
cql.execute(f'INSERT INTO {table_ttl_1} (p, v) VALUES ({p2}, 1)')
|
|
# p2 item should expire in *less* than one second (it will expire
|
|
# in the next whole second),
|
|
start = time.time()
|
|
while len(list(cql.execute(f'SELECT * from {table_ttl_1} where p={p2}'))):
|
|
assert time.time() < start + 2
|
|
time.sleep(0.1)
|
|
# p1 should not have expired yet. By the way, its current ttl(v) would
|
|
# normally be exactly 999 now, but theoretically could be a bit lower in
|
|
# case of delays in the test.
|
|
assert len(list(cql.execute(f'SELECT *from {table_ttl_1} where p={p1}'))) == 1
|
|
|
|
# Above we tested that explicitly setting "using ttl" overrides the default
|
|
# ttl set for the table. Here we check that also in the special case of
|
|
# "using ttl 0" (which means the item should never expire) it also overrides
|
|
# the default TTL. Reproduces issue #9842.
|
|
def test_default_ttl_0_override(cql, table_ttl_100):
|
|
p = unique_key_int()
|
|
cql.execute(f'INSERT INTO {table_ttl_100} (p, v) VALUES ({p}, 1) USING TTL 0')
|
|
# We can immediately check that this item's TTL is "null", meaning it
|
|
# will never expire. There's no need to have any sleeps.
|
|
assert list(cql.execute(f'SELECT ttl(v) from {table_ttl_100} where p={p}')) == [(None,)]
|
|
|
|
# Whereas a zero TTL overrides the default TTL, an unset TTL doesn't - and
|
|
# leaves the default TTL. This means that the text in Cassandra's NEWS.txt
|
|
# which claims that "an unset bind ttl is treated as 'unlimited'" is not
|
|
# accurate - it's only unlimited if there is no default TTL for the table,
|
|
# and if there is, this default TTL is used instead of unlimited. In other
|
|
# words, an UNSET_VALUE TTL behaves exactly like not specifying a TTL at all.
|
|
# See also test_unset.py::test_unset_ttl()
|
|
def test_default_ttl_unset_override(cql, table_ttl_100):
|
|
p = unique_key_int()
|
|
stmt = cql.prepare(f'INSERT INTO {table_ttl_100} (p, v) VALUES ({p}, 1) USING TTL ?')
|
|
cql.execute(stmt, [UNSET_VALUE])
|
|
# At this point, reading ttl(v) would normally return 99, but it's
|
|
# possible in case of delays to be somewhat lower. But it wouldn't
|
|
# be None - which would mean that the item will never expire.
|
|
assert list(cql.execute(f'SELECT ttl(v) from {table_ttl_100} where p={p}')) != [(None,)]
|