[
https://issues.apache.org/jira/browse/FLINK-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523738#comment-16523738
]
ASF GitHub Bot commented on FLINK-8983:
---------------------------------------
Github user medcv commented on the issue:
https://github.com/apache/flink/pull/6083
@tillrohrmann
here is my two cents:
By converting the events to `String` and sending them to Kafka there is a
high risk to produce a `bad events` and we will lose the benifit of Schema
Registry to avoid this malformed events sent to the topic.
what you think about `AvroSerializationConfluentSchema` to Flink dist? If
we move this serialization code in Flink dist we can drop `kafka-avro`
dependencies from here.
but still if you think using `String` is ok I can update the PR and use
`String` instead of `AvroSerializationConfluentSchema`
> End-to-end test: Confluent schema registry
> ------------------------------------------
>
> Key: FLINK-8983
> URL: https://issues.apache.org/jira/browse/FLINK-8983
> Project: Flink
> Issue Type: Sub-task
> Components: Kafka Connector, Tests
> Reporter: Till Rohrmann
> Assignee: Yazdan Shirvany
> Priority: Critical
> Labels: pull-request-available
>
> It would be good to add an end-to-end test which verifies that Flink is able
> to work together with the Confluent schema registry. In order to do that we
> have to setup a Kafka cluster and write a Flink job which reads from the
> Confluent schema registry producing an Avro type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
