branhoff opened a new issue #12574: URL: https://github.com/apache/pulsar/issues/12574
**Describe the bug** When generating a schema definition with the same fields as a topic's registered schema, if the the generated schema is in a different order than the registered schema, will be labeled as incompatible. **To Reproduce** Steps to reproduce the behavior: 1. Go to https://github.com/ta1meng/pulsar-python-avro-schema-examples 2. Read the `README` file at the root directory as well as `README` file in: * example02_nested_schema 3. Change the order of the `MySubRecord` instance arguments in the producer to be out of sync with the `MySubRecord` class 4. RRun the `producer` and `consumer` in the pulsar standalone environment **Expected behavior** The documented [example](https://pulsar.apache.org/docs/fr/client-libraries-python/#complex-types) should work out of the box. There should be support for common Avro keywords like `doc`. **Screenshots** N/A **Desktop (please complete the following information):** OS: MacOS **Additional context** Tested against Pulsar 2.7.2 and Pulsar 2.8.1. Using both Python Pulsar client 2.7.2 and Pulsar 2.8.1 under Python 3.7. Issue originally reported in ticket [#10596](https://github.com/apache/pulsar/issues/10596) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
