momo-jun commented on code in PR #18242: URL: https://github.com/apache/pulsar/pull/18242#discussion_r1013654236
########## site2/docs/schema-evolution-compatibility.md: ########## @@ -6,29 +6,21 @@ sidebar_label: "Schema evolution and compatibility" Normally, schemas do not stay the same over a long period of time. Instead, they undergo evolutions to satisfy new needs. -This chapter examines how Pulsar schema evolves and what Pulsar schema compatibility check strategies are. +This chapter introduces how Pulsar schema evolves and what compatibility check strategies it adopts. ## Schema evolution -Pulsar schema is defined in a data structure called `SchemaInfo`. - -Each `SchemaInfo` stored with a topic has a version. The version is used to manage the schema changes happening within a topic. - The message produced with `SchemaInfo` is tagged with a schema version. When a message is consumed by a Pulsar client, the Pulsar client can use the schema version to retrieve the corresponding `SchemaInfo` and use the correct schema information to deserialize data. -### What is schema evolution? - Schemas store the details of attributes and types. To satisfy new business requirements, you need to update schemas inevitably over time, which is called **schema evolution**. Any schema changes affect downstream consumers. Schema evolution ensures that the downstream consumers can seamlessly handle data encoded with both old schemas and new schemas. -### How Pulsar schema should evolve? - -The answer is Pulsar schema compatibility check strategy. It determines how schema compares old schemas with new schemas in topics. +### How schema evolves? -For more information, see [Schema compatibility check strategy](#schema-compatibility-check-strategy). +The answer is [schema compatibility check strategy](#schema-compatibility-check-strategy). It determines how schema compares old schemas with new schemas in topics. Review Comment: Indeed. Can be considered and improved in the content review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
