You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (Jira)" <ji...@apache.org> on 2026/04/20 16:20:00 UTC
[jira] [Created] (CASSSIDECAR-432) Validate schema during configuration updates
Paulo Motta created CASSSIDECAR-432:
---------------------------------------
Summary: Validate schema during configuration updates
Key: CASSSIDECAR-432
URL: https://issues.apache.org/jira/browse/CASSSIDECAR-432
Project: Sidecar for Apache Cassandra
Issue Type: Task
Reporter: Paulo Motta
CEP-62 requires that configuration updates to \{{cassandraYaml}} are validated against the version-aware JSON Schema for the instance's Cassandra major version. When the Configuration Manager processes an update, it fetches the Cassandra version from the \{{LifecycleProvider}} for the target instance, loads the corresponding schema, and rejects updates that introduce unknown keys or type mismatches. \{{extraJvmOpts}} values are opaque JVM arguments and bypass schema validation. If the Cassandra version cannot be determined, updates modifying \{{cassandraYaml}} are rejected.
Acceptance Criteria:
- Cassandra version is fetched from the \{{LifecycleProvider}} for the target instance.
- Configuration updates are validated against the JSON Schema matching the instance's Cassandra major version.
- Unknown \{{cassandraYaml}} keys are rejected.
- Type mismatches are rejected.
- \{{extraJvmOpts}} values are not subject to schema validation.
- Updates modifying \{{cassandraYaml}} are rejected when the Cassandra version cannot be determined.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org