nodece commented on code in PR #15887:
URL: https://github.com/apache/pulsar/pull/15887#discussion_r887621175
##########
site2/docs/schema-evolution-compatibility.md:
##########
@@ -30,19 +30,34 @@ For more information, see [Schema compatibility check
strategy](#schema-compatib
### How does Pulsar support schema evolution?
-1. When a producer/consumer/reader connects to a broker, the broker deploys
the schema compatibility checker configured by
`schemaRegistryCompatibilityCheckers` to enforce schema compatibility check.
+The process of how Pulsar supports schema evolution is described as follows.
- The schema compatibility checker is one instance per schema type.
+1. The producer/consumer/reader sends its client `SchemaInfo` to brokers.
- Currently, Avro and JSON have their own compatibility checkers, while all
the other schema types share the default compatibility checker which disables
schema evolution.
+2. Brokers recognize the schema type and deploy the schema compatibility
checker `schemaRegistryCompatibilityCheckers` for that schema type to enforce
schema compatibility check.
Review Comment:
I suggest adding `schemaRegistryCompatibilityCheckers` config here, so like:
```
schemaRegistryCompatibilityCheckers=org.apache.pulsar.broker.service.schema.JsonSchemaCompatibilityCheck,org.apache.pulsar.broker.service.schema.AvroSchemaCompatibilityCheck,org.apache.pulsar.broker.service.schema.ProtobufNativeSchemaCompatibilityCheck
```
--
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]
