[
https://issues.apache.org/jira/browse/CASSSIDECAR-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSSIDECAR-429:
------------------------------------
Description:
Implement the PATCH configuration flow in the Configuration Manager as defined
in CEP-62. The manager should acquire a per-instance exclusive lock, validate
the expectedHash against the current effective configuration hash, apply JSON
Patch operations to compute the updated overlay, persist it via the
ConfigurationProvider, and return the new effective configuration with updated
hash and timestamp.
Version-aware schema validation, immutable settings blocklist, and failure
policy handling will be added in follow-up tasks.
was:
Implement the PATCH configuration flow in the Configuration Manager as defined
in CEP-62. The manager should acquire a per-instance exclusive lock, validate
the expectedHash against the current effective configuration hash, apply JSON
Patch operations to compute the updated overlay, persist it via the
ConfigurationProvider, and return the new effective configuration with updated
hash and timestamp.
After persisting to the provider, the manager should update the cached
overlay.json and rematerialize cassandra.yaml and extra-jvm.options in the
configuration store.
Version-aware schema validation, immutable settings blocklist, and failure
policy handling will be added in follow-up tasks.
> Implement basic configuration update in ConfigurationManager
> ------------------------------------------------------------
>
> Key: CASSSIDECAR-429
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-429
> Project: Sidecar for Apache Cassandra
> Issue Type: Task
> Reporter: Paulo Motta
> Priority: Major
>
> Implement the PATCH configuration flow in the Configuration Manager as
> defined in CEP-62. The manager should acquire a per-instance exclusive lock,
> validate the expectedHash against the current effective configuration hash,
> apply JSON Patch operations to compute the updated overlay, persist it via
> the ConfigurationProvider, and return the new effective configuration with
> updated hash and timestamp.
>
> Version-aware schema validation, immutable settings blocklist, and failure
> policy handling will be added in follow-up tasks.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]