Uploaded image for project: 'Kafka Connector'
  1. Kafka Connector
  2. KAFKA-210

Ensure deterministic schema names

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.5.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Needed
    • Hide

      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 KAFKA-210.

      KAFKA-210 ensures that the inferred schema naming convention should allow for possible compatibility in the future.

      Users relying on the previous inferred schema definitions will have to explicitly define it in their configuration.

      Show
      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 KAFKA-210 . KAFKA-210 ensures that the inferred schema naming convention should allow for possible compatibility in the future. Users relying on the previous inferred schema definitions will have to explicitly define it in their configuration.

      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.

            Assignee:
            ross@mongodb.com Ross Lawley
            Reporter:
            ross@mongodb.com Ross Lawley
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: