title: Schema registry incompatible changes
body: <p>In all the documentation it’s clear described how to handle compatible changes with Schema Registry with compatibility types.<br />
  But how to introduce incompatible changes without disturbing the downstream consumers directly, so that the can migrated in their own pace?<br />
  We have the following situation (see image) where the producer is producing the same message in both schema versions:</p>
  <p><a href="https://i.stack.imgur.com/afLMW.jpg" rel="nofollow noreferrer">Image</a></p>
  <p>The problem is how to migrated the app’s and the sink connector in a controlled way, where business continuity is important and the consumer are not allowed to process  the same message (in the new format).</p>