You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/08/01 02:12:49 UTC

[GitHub] [pulsar] sijie commented on a change in pull request #4841: [Doc] Add Schema Evolution and Compatibility section

sijie commented on a change in pull request #4841: [Doc] Add Schema Evolution and Compatibility section
URL: https://github.com/apache/pulsar/pull/4841#discussion_r309487303
 
 

 ##########
 File path: site2/docs/schema-evolution-compatibility.md
 ##########
 @@ -0,0 +1,165 @@
+---
+id: schema-evolution-compatibility
+title: Schema evolution and compatibility
+sidebar_label: Schema evolution and compatibility
+---
+
+## 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.
+
+For more information, see [Schema compatibility check strategy](#schema-compatibility-check-strategy).
+
 
 Review comment:
   That's correct.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services