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 2021/08/11 05:50:54 UTC

[GitHub] [pulsar] Zhen-hao commented on issue #11631: schema compatibility check overly restrictive

Zhen-hao commented on issue #11631:
URL: https://github.com/apache/pulsar/issues/11631#issuecomment-896521118


   OK. I think I know the real issue here.
   
   [The Pulsar documentation](https://pulsar.apache.org/docs/en/schema-evolution-compatibility/) makes it clear
   ```
   For Avro and JSON, the default schema compatibility check strategy is FULL.
   ```
   
   My problem is to find a way to set the default compatibility level to `BACKWARD` on the namespace level. Because I need to create a lot of topics dynamically.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org