You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading from v6.2.1 to v7.5.2 confluent-community edition Kafka Connect, I encountered the error: “Mismatched names: name already added to SchemaBuilder (org.apache.kafka.connect.data.Decimal) differs from name in source schema (avro.customnamespace.BP)” . This occurred when testing JDBC and s3 sink connectors reading from a Kafka topic, which reads avro Schemas stored in Schema Registry.
Add field “connect.name”: “org.apache.kafka.connect.data.Decimal” → This does not affect the Kafka Topic message, but does require changing schema in Schema Registry
Remove name & namespace for field schema → No error but changes the field name in the Kafka topic message
Downgrading kafka-connect-avro-data jar to 6.2.6 or below → Do not need to change anything else for this fix, but unsure if there are other side effects of downgrading one specific jar and also just a bad practice, but does not require changing the Schema or affect the data
My question is:
a. Are there any other better approaches/solutions to the above?
b. Are having named fields for decimal logical type fields intended to be allowed, or is it more correct to remove that (ie option 1 or 3?)
The text was updated successfully, but these errors were encountered:
After upgrading from v6.2.1 to v7.5.2 confluent-community edition Kafka Connect, I encountered the error: “Mismatched names: name already added to SchemaBuilder (org.apache.kafka.connect.data.Decimal) differs from name in source schema (avro.customnamespace.BP)” . This occurred when testing JDBC and s3 sink connectors reading from a Kafka topic, which reads avro Schemas stored in Schema Registry.
An example of the failing schema:
The solutions I have tested to work are:
My question is:
a. Are there any other better approaches/solutions to the above?
b. Are having named fields for decimal logical type fields intended to be allowed, or is it more correct to remove that (ie option 1 or 3?)
The text was updated successfully, but these errors were encountered: