ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When an API producer marks a schema property as deprecated and later removes it, the OpenAPI document evolves. Rolling back that change—re‑adding the property while keeping the deprecated flag—raises questions about whether existing client code generated from the earlier spec will still validate without modification. The goal is to determine if a rolled‑back
The goal is to assess if a Flink job can be safely rolled back to a pre‑change schema after a breaking modification (e.g., field removal or type change) when using the savepoint compatibility mode introduced in Flink 1.16. Current documentation states that automatic restoration is only possible for backward‑compatible schema evolutions; for breaking changes
Goal Upgrade a small Java application’s ClickHouse schema without service interruption. The application uses the official JDBC driver and a ReplicatedMergeTree table that must stay writable during the change. Constraints ALTER TABLE ADD COLUMN with a default value temporarily locks writes on the shard. Drop‑and‑swap requires a brief window where the old tabl
Schema Evolution in Akka Persistence When updating the event schema for a Persistent Actor, the primary goal is ensuring that a previous binary version can still recover state if a deployment must be rolled back after new events have been written to the journal. The Compatibility Constraint Akka Persistence provides EventAdapter and upcaster chains to handle
Rollback safety after schema change The goal is to revert a Pulsar topic to a prior schema version without corrupting or losing data that was produced under the newer schema. Pulsar’s schema evolution supports backward, forward, and full compatibility modes for Avro, JSON, and Protobuf, yet no native transactional rollback exists. Producers and consumers mus
When a breaking schema change must be rolled back, teams need a versioning approach that lets them revert to the previous contract without breaking existing clients while still enabling automated compatibility checks. The OpenAPI Specification offers two common patterns: URI versioning (e.g., /v1/resource) and header versioning (e.g., Accept: application/vnd
Aerospike employs a schema-less architecture where record structures are defined at the application layer rather than the server level. When evolving data models, developers often implement an "Expand and Contract" pattern to transition from an old bin to a new bin without downtime. A critical challenge arises during the transition phase where the applicatio
openapi
processing
clickhouse
akka
pulsar
swagger
aerospike