ta1meng edited a comment on issue #9571: URL: https://github.com/apache/pulsar/issues/9571#issuecomment-781602346
This might be a duplicate of https://github.com/apache/pulsar/issues/8510. I ran into the same issues using the Java client. Primary issue: I believe that the above two schema versions are not identical. They likely contain a whitespace difference. Unfortunately, Pulsar seems to consider two schema definitions that differ by whitespace different, and compatible. If aligning the whitespacing of the schema definitions resolve your problem, please mark this ticket a duplicate of https://github.com/apache/pulsar/issues/8510. -- You are right to disable auto updates. If the above worked, you don't have to read the below text. I'm sharing with you how I set the various schema policies for your reference. I've not had anyone review these policy settings, so if you see something dubious, feel free to ask me to elaborate. `bin/pulsar-admin namespaces set-is-allow-auto-update-schema --disable <tenant/namespace>` `bin/pulsar-admin namespaces set-schema-compatibility-strategy <tenant/namespace> --compatibility FORWARD_TRANSITIVE` `bin/pulsar-admin namespaces set-schema-validation-enforce --enable <tenant/namespace>` `bin/pulsar-admin namespaces set-schema-autoupdate-strategy <tenant/namespace> --disabled` The schema related policies for my namespace look like: `bin/pulsar-admin namespaces policies <tenant/namespace>` `"schema_auto_update_compatibility_strategy" : "AutoUpdateDisabled", "schema_compatibility_strategy" : "FORWARD_TRANSITIVE", "is_allow_auto_update_schema" : false, "schema_validation_enforced" : true` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
