[
https://issues.apache.org/jira/browse/KAFKA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis resolved KAFKA-7688.
-------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1.1)
This issue was resolved outside the Apache Kafka repo with this fix:
[https://github.com/confluentinc/schema-registry/pull/1020
]Feel free to re-open if there's still missing functionality that belongs
strictly to the Kafka Connect framework.
> Allow byte array class for Decimal Logical Types to fix Debezium Issues
> -----------------------------------------------------------------------
>
> Key: KAFKA-7688
> URL: https://issues.apache.org/jira/browse/KAFKA-7688
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 1.1.1
> Reporter: Eric C Abis
> Priority: Blocker
>
> Decimal Logical Type fields are failing with Kafka Connect sink tasks and
> showing this error:
> {code:java}
> Invalid Java object for schema type BYTES: class [B for field: "null"{code}
> There is an issue tracker for the problem here in the Confluent Schema
> Registry tracker (it's all related):
> [https://github.com/confluentinc/schema-registry/issues/833]
> I've created a fix for this issue and tested and verified it in our CF4
> cluster here at Shutterstock.
> The issue boils down to the fact that Avro Decimal Logical types store values
> as a Byte Arrays. Debezium sets the Default Value as Base64 encoded Byte
> Arrays and record values as Big Integer Byte Arrays. I'd like to submit a
> PR that changes the SCHEMA_TYPE_CLASSES hash map in
> org.apache.kafka.connect.data.ConnectSchema to allow Byte Arrays for Decimal
> fields.
> I reached out [to
> [email protected]|mailto:to%c2%[email protected]] to ask for
> GitHub permissions but if there is somewhere else I need to reach out to
> please let me know.
> My GitHub user is TheGreatAbyss
> Thank You!
> Eric
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
