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 2018/10/05 02:45:43 UTC

[GitHub] sijie opened a new pull request #2730: [schema] provide a flag to disable/enable schema validation on broker and change default bytes producer to use `AUTO_PRODUCE_BYTES`

sijie opened a new pull request #2730: [schema] provide a flag to disable/enable schema validation on broker and change default bytes producer to use `AUTO_PRODUCE_BYTES`
URL: https://github.com/apache/pulsar/pull/2730
 
 
   
   
   *Motivation*
   
   We need an upgrade/backward compatibility story for schema enforcement. Especially around:
   
   - `Producers cannot connect without a schema to topics with a schema`
   
   *Changes*
   
   - provide a flag on brokers to enable schema validation (and disabled it by default). this allows a smooth upgrade on brokers,
     otherwise, it will break all non-java producers on topics with schema immediately when upgrade to the new version
   - change the default bytes producer to use `AUTO_PRODUCE_BYTES`. this would introduce performance penalty for producers without
     schema producing messages to topics with schema, however that is probably rare. since the world beforce schema, topics don't
     have schema, so there is no validation happen; the world after schema, new clients are starting using the typed api where
     schema is already enforced. introducing `AUTO_PRODUCE_BYTES` also provides a better story for people to enable validation
     on broker side, since there is no really change will need if client already support AUTO_PRODUCE_BYTES
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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