zone_config

# LogicTest: !3node-tenant(49854)
# Check that we can alter the default zone config.

statement ok
ALTER RANGE default CONFIGURE ZONE USING num_replicas = 1

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR RANGE default]
----
0  ALTER RANGE default CONFIGURE ZONE USING
   range_min_bytes = 134217728,
   range_max_bytes = 536870912,
   gc.ttlseconds = 90000,
   num_replicas = 1,
   constraints = '[]',
   lease_preferences = '[]'

# Check that we can reset the default zone config to defaults.

statement ok
ALTER RANGE default CONFIGURE ZONE USING DEFAULT

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR RANGE default]
----
0  ALTER RANGE default CONFIGURE ZONE USING
   range_min_bytes = 134217728,
   range_max_bytes = 536870912,
   gc.ttlseconds = 90000,
   num_replicas = 3,
   constraints = '[]',
   lease_preferences = '[]'

# Make an override for the tests below

statement ok
ALTER RANGE default CONFIGURE ZONE USING range_min_bytes = 1234567

statement ok
CREATE TABLE a (id INT PRIMARY KEY)

# Ensure that SHOW ZONE CONFIGURATION retrieves the default zone (ID 0) if
# no zone was set.
query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
0  ALTER RANGE default CONFIGURE ZONE USING
   range_min_bytes = 1234567,
   range_max_bytes = 536870912,
   gc.ttlseconds = 90000,
   num_replicas = 3,
   constraints = '[]',
   lease_preferences = '[]'

# Once USING DEFAULT has been used, we get the default config
# but with our own zone config ID.

statement ok
ALTER TABLE a CONFIGURE ZONE USING DEFAULT

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 90000,
    num_replicas = 3,
    constraints = '[]',
    lease_preferences = '[]'

# Check that configurations can be adjusted with USING.
statement ok
ALTER TABLE a CONFIGURE ZONE USING
  range_min_bytes = 200000 + 1,
  range_max_bytes = 300000 + 1,
  gc.ttlseconds = 3000 + 600,
  num_replicas = floor(1.2)::int,
  constraints = '[+region=test]',
  lease_preferences = '[[+region=test]]'

# This should reflect in the metrics.
query T
SELECT feature_name FROM crdb_internal.feature_usage
WHERE feature_name IN (
  'sql.schema.zone_config.table.range_min_bytes',
  'sql.schema.zone_config.table.range_max_bytes',
  'sql.schema.zone_config.table.gc.ttlseconds',
  'sql.schema.zone_config.table.num_replicas',
  'sql.schema.zone_config.table.constraints'
) AND usage_count > 0 ORDER BY feature_name
----
sql.schema.zone_config.table.constraints
sql.schema.zone_config.table.gc.ttlseconds
sql.schema.zone_config.table.num_replicas
sql.schema.zone_config.table.range_max_bytes
sql.schema.zone_config.table.range_min_bytes

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 200001,
    range_max_bytes = 300001,
    gc.ttlseconds = 3600,
    num_replicas = 1,
    constraints = '[+region=test]',
    lease_preferences = '[[+region=test]]'

# Check that we can set just one value without altering the others.
statement ok
ALTER TABLE a CONFIGURE ZONE USING range_max_bytes = 400000

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 200001,
    range_max_bytes = 400000,
    gc.ttlseconds = 3600,
    num_replicas = 1,
    constraints = '[+region=test]',
    lease_preferences = '[[+region=test]]'

# Check that we can configure zones in tables in non-public schemas, and that
# they don't conflict with tables of the same name in different schemas.

statement ok
CREATE SCHEMA test

statement ok
CREATE TABLE test.a (a INT PRIMARY KEY)

statement ok
ALTER TABLE test.a CONFIGURE ZONE USING gc.ttlseconds=1234

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE test.a]
----
55  ALTER TABLE test.a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 1234,
    num_replicas = 3,
    constraints = '[]',
    lease_preferences = '[]'

# Check that the original table's zone config is unmodified.

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 200001,
    range_max_bytes = 400000,
    gc.ttlseconds = 3600,
    num_replicas = 1,
    constraints = '[+region=test]',
    lease_preferences = '[[+region=test]]'

# Check that we can reset the configuration to defaults.

statement ok
ALTER TABLE a CONFIGURE ZONE USING DEFAULT

# Note: the range_min_bytes here should reflect the non-standard
# default that was set initially.
query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 90000,
    num_replicas = 3,
    constraints = '[]',
    lease_preferences = '[]'

# Check that we can drop a configuration to get back to inherinting
# the defaults.
statement ok
ALTER TABLE a CONFIGURE ZONE DISCARD

query I
SELECT zone_id FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
0

subtest alter_table_telemetry

query T
SELECT feature_name FROM crdb_internal.feature_usage
WHERE feature_name IN ('sql.schema.alter_range.configure_zone', 'sql.schema.alter_table.configure_zone')
ORDER BY feature_name
----
sql.schema.alter_range.configure_zone
sql.schema.alter_table.configure_zone


# Check that configuring num_voters separately from num_replicas behaves as
# expected, across setting them directly and through inheritance.
#
# 1. Check that voter_constraints cannot be set without setting num_voters as
# well.
statement error pq: could not validate zone config: when voter_constraints are set, num_voters must be set as well
ALTER TABLE a CONFIGURE ZONE USING voter_constraints = '{"+region=test": 3}'

# 2. Check that num_voters and voter_constraints show up in tandem once
# num_voters is explicitly set.
statement ok
ALTER TABLE a CONFIGURE ZONE USING num_replicas = 3;

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 90000,
    num_replicas = 3,
    constraints = '[]',
    lease_preferences = '[]'

statement ok
ALTER TABLE a CONFIGURE ZONE USING num_voters = 1;

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 90000,
    num_replicas = 3,
    num_voters = 1,
    constraints = '[]',
    voter_constraints = '[]',
    lease_preferences = '[]'

# 3. Sanity check that `voter_constraints` can be reset.
statement ok
ALTER TABLE a CONFIGURE ZONE USING voter_constraints = '{"+region=test": 1}'

statement error pq: constraint "\+region=shouldFail" matches no existing nodes within the cluster - did you enter it correctly\?
ALTER TABLE a CONFIGURE ZONE USING voter_constraints = '{"+region=shouldFail": 1}'

# 3.1 Ensure that when copying num_voters from a parent that does not have
# num_voters explicitly configured,  we copy the parent's num_replicas value
# instead.
statement ok
ALTER TABLE a CONFIGURE ZONE USING num_voters = COPY FROM PARENT

query IT
SELECT zone_id, raw_config_sql FROM [SHOW ZONE CONFIGURATION FOR TABLE a]
----
53  ALTER TABLE a CONFIGURE ZONE USING
    range_min_bytes = 1234567,
    range_max_bytes = 536870912,
    gc.ttlseconds = 90000,
    num_replicas = 3,
    num_voters = 3,
    constraints = '[]',
    voter_constraints = '{+region=test: 1}',
    lease_preferences = '[]'