[
https://issues.apache.org/jira/browse/KAFKA-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315110#comment-17315110
]
Randall Hauch commented on KAFKA-10715:
---------------------------------------
There are multiple Converter implementations outside of Kafka, and IMO there is
no need for Kafka to own and maintain its own version of these when those other
existing implementations can easily be used by simply installing them.
This is similar to how the Kafka project provides only example Connector
implementations. See the [rejected alternatives of
KIP-26|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=58851767#KIP26AddKafkaConnectframeworkfordataimport/export-Maintainconnectorsintheprojectalongwithframework],
which introduced the Connect framework (with Converters).
Therefore, I'm going to close this.
> Support Kafka connect converter for AVRO
> ----------------------------------------
>
> Key: KAFKA-10715
> URL: https://issues.apache.org/jira/browse/KAFKA-10715
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect
> Reporter: Ravindranath Kakarla
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> I want to add support for Avro data format converter to Kafka Connect. Right
> now, Kafka connect supports [JSON
> converter|[https://github.com/apache/kafka/tree/trunk/connect].] Since, Avro
> is a commonly used data format with Kafka, it will be great to have support
> for it.
>
> Confluent Schema Registry libraries have
> [support|https://github.com/confluentinc/schema-registry/blob/master/avro-converter/src/main/java/io/confluent/connect/avro/AvroConverter.java]
> for it. The code seems to be pretty generic and can be used directly with
> Kafka connect without schema registry. They are also licensed under Apache
> 2.0.
>
> Can they be copied to this repository and made available for all users of
> Kafka Connect?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
