[ 
https://issues.apache.org/jira/browse/FLINK-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-4050:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: 
auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> FlinkKafkaProducer API Refactor
> -------------------------------
>
>                 Key: FLINK-4050
>                 URL: https://issues.apache.org/jira/browse/FLINK-4050
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>    Affects Versions: 1.0.3
>            Reporter: Elias Levy
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> The FlinkKafkaProducer API seems more difficult to use than it should be.  
> The API requires you pass it a SerializationSchema or a 
> KeyedSerializationSchema, but the Kafka producer already has a serialization 
> API.  Requiring a serializer in the Flink API precludes the use of the Kafka 
> serializers.  For instance, they preclude the use of the Confluent 
> KafkaAvroSerializer class that makes use of the Confluent Schema Registry.  
> Ideally, the serializer would be optional, so as to allow the Kafka producer 
> serializers to handle the task.
> In addition, the KeyedSerializationSchema conflates message key extraction 
> with key serialization.  If the serializer were optional, to allow the Kafka 
> producer serializers to take over, you'd still need to extract a key from the 
> message.
> And given that the key may not be part of the message you want to write to 
> Kafka, an upstream step may have to package the key with the message to make 
> both available to the sink, for instance in a tuple. That means you also need 
> to define a method to extract the message to write to Kafka from the element 
> passed into the sink by Flink.  
> In summary, there should be separation of extraction of the key and message 
> from the element passed into the sink from serialization, and the 
> serialization step should be optional.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to