Safe Schema Evolution with Apache Pulsar's Schema Registry
Learn how Pulsar's Schema Registry enforces compatibility checks to let you evolve Avro schemas safely without breaking consumers.
Loading…
ReadMeFeed / Community knowledge
#avro
Real questions. Useful conversations. Find the people who know your stack.
Pulsar's Schema Registry: Evolving Event Schemas Without Breaking Consumers
Pulsar's built-in schema registry enforces compatibility at the broker, turning schema evolution from a production incident into a controlled operation. Here's how the policies work and where they bite.
Stopping Schema Drift in Streaming Pipelines with Pulsar's Built-In Schema Registry
Schema drift corrupts streaming data silently. Pulsar's built-in schema registry enforces compatibility broker-side — here's how it works, an Avro example, and the trade-offs.
Using Pulsar Schema Registry to Prevent Silent Data Corruption
Learn how Apache Pulsar’s built‑in Schema Registry centralizes schema validation, enforces compatibility, and reduces integration bugs in event‑driven pipelines.
Choosing Between Parquet and Avro for Spark ETL Pipelines
A technical decision guide for choosing between Parquet and Avro in Apache Spark, comparing read/write performance, schema evolution, and columnar vs. row-based storage.
Schema mismatch: expected field X of type Y, found Z after LinkedIn online DDL rollback
Schema mismatch after LinkedIn online DDL rollback The goal is to guarantee that a rollback of an online DDL schema change does not leave consumers deserializing data with the newer Avro schema, which currently produces errors such as “Schema mismatch: expected field X of type Y, found Z”. LinkedIn’s internal online DDL tool applies changes incrementally but
linkedin