[KAFKA-210] Ensure deterministic schema names Created: 22/Mar/21 Updated: 28/Oct/23 Resolved: 23/Mar/21 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Needed |
| Documentation Changes Summary: | An upgrade notice is required for this change. Users relying on previously inferred schema definitions may find future compatibility with the Schema Registry breaks compatibility as a result of https://github.com/confluentinc/schema-registry/pull/1775 and the fix in
Users relying on the previous inferred schema definitions will have to explicitly define it in their configuration. |
| Description |
|
Due to recent SR changes, the schemas, generated by MongoDB, have been found to be backward incompatible. Previously the naming convention for fields used was based off the hashcode from the Schema. If an optional field wasn't included a document it would produce different schema names. With the future coming changes to Schema Registry, such naming is not backward compatible. Working with Rajendra Dangwal from confluent it was determined using the fieldname for any nested fields works better and then the top level name can be "default". More details in the PR. |
| Comments |
| Comment by Githook User [ 23/Mar/21 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Fix inferred schema naming conventions Ensures that schemas can be backwards compatible if
|