GitHub user rhauch opened a pull request: https://github.com/apache/kafka/pull/3198
KAFKA-5164 Ensure SetSchemaMetadata updates key or value when Schema changes When the `SetSchemaMetadata` SMT is used to change the name and/or version of the key or valueâs schema, any references to the old schema in the key or value must be changed to reference the new schema. Only keys or values that are `Struct` have such references, and so currently only these are adjusted. This is based on `trunk` since the fix is expected to be targeted to the 0.11.1 release. You can merge this pull request into a Git repository by running: $ git pull https://github.com/rhauch/kafka kafka-5164 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3198.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3198 ---- commit 68bf68b3df065437318e2a87a6d1181b1205a806 Author: Randall Hauch <rha...@gmail.com> Date: 2017-06-01T20:40:01Z KAFKA-5164 Ensure SetSchemaMetadata updates key or value when Schema changes When the `SetSchemaMetadata` SMT is used to change the name and/or version of the key or valueâs schema, any references to the old schema in the key or value must be changed to reference the new schema. Only keys or values that are `Struct` have such references, and so currently only these are adjusted. ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---