jon-hanson opened a new issue, #15855:
URL: https://github.com/apache/pulsar/issues/15855

   ### What issue do you find in Pulsar docs?
   
   Regarding schema evolution, the [Pulsar 
documentation](https://pulsar.apache.org/docs/schema-evolution-compatibility#how-does-pulsar-support-schema-evolution)
 states the following:
   
   > **How does Pulsar support schema evolution?**
   >
   > When a producer/consumer/reader connects to a broker, the broker deploys 
the schema compatibility checker configured by 
_schemaRegistryCompatibilityCheckers_ to enforce schema compatibility check.
   
   What exactly is "schemaRegistryCompatibilityCheckers" and where is it 
configured? The term seems to appear out of the blue without any context.
   
   It isn't referenced anywhere else in the documentation as far as I can see. 
If I search for the term online all I find is a 
[reference](https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/schema/SchemaRegistryService.java#L45)
 in the Pulsar codebase (specifically a parameter to the 
SchemaRegistryService.create method):
   
       static SchemaRegistryService create(SchemaStorage schemaStorage, 
Set<String> schemaRegistryCompatibilityCheckers) {
   
   The documentation doesn't appear to be suggesting that I should be calling 
this method, so what does it mean?
   
   ### What is your suggestion?
   
   The documentation should make clear what exactly 
"schemaRegistryCompatibilityCheckers" is and where it is defined/configured. A 
code example would help enormously.
   
   ### Do you have any references?
   
   N/A
   
   ### Would you like to fix this issue?
   
   I would if I knew the answer.
   
   ### Note
   
   - [X] I have researched my question.


-- 
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]

Reply via email to