From commits-return-15661-archive-asf-public=cust-asf.ponee.io@pulsar.apache.org Fri Oct 5 04:45:45 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 88E80180677 for ; Fri, 5 Oct 2018 04:45:45 +0200 (CEST) Received: (qmail 68149 invoked by uid 500); 5 Oct 2018 02:45:44 -0000 Mailing-List: contact commits-help@pulsar.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pulsar.apache.org Delivered-To: mailing list commits@pulsar.apache.org Received: (qmail 68129 invoked by uid 99); 5 Oct 2018 02:45:43 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2018 02:45:43 +0000 From: GitBox To: commits@pulsar.apache.org Subject: [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` Message-ID: <153870754327.17808.17152133046263081793.gitbox@gitbox.apache.org> Date: Fri, 05 Oct 2018 02:45:43 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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