Hi, Are you referring to this topic level config? message.format.version
Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. So in my case since broker is of version 0.10.2 by default every topic is created with this format? A default producer of that version will publish message of this format? And as a result a client of older version is not able to consume message of this format from that topic? Am I right in understanding the case? Also in my case for this to work I need to set message.format.version = 0.8.2 for that topic and produce message from my default 0.10.2 client. Then the consumer client using version 0.8.2 will correct consume message produced by that producer. Is this correct way of handling this case? Thanks Sachin On Wed, Jul 19, 2017 at 5:43 PM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi Sachin, > > Yes, that should work as the broker will down convert the messages for the > older consumer. The one thing to avoid is decreasing the message format > version for an existing topic. That is not supported. > > As usual, you should test this in a non production environment first. Also, > one additional comment inline. > > On Wed, Jul 19, 2017 at 1:19 AM, Sachin Mittal <sjmit...@gmail.com> wrote: > > > > I btw have doubt that different versions work on same topic as message > > format has changed from 0.8.x through 0.11.x > > > > This should work fine, we have tests that update the message format version > while clients are producing/consuming to verify this scenario. > > Ismael >
