[ 
https://issues.apache.org/jira/browse/FLINK-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013638#comment-15013638
 ] 

ASF GitHub Bot commented on FLINK-3045:
---------------------------------------

GitHub user rmetzger opened a pull request:

    https://github.com/apache/flink/pull/1385

    [FLINK-3045] Properly expose the key of a Kafka message

    The current Kafka connector does not allow users to access the message key.
    
    With this change, I've added a new pair of serialization schemas 
(`KeyedDeserializationSchema` and `KeyedSerializationSchema`) a utiliy to 
create Kafka serializers from Flink's TypeInformation system: 
`TypeInformationKeyValueSerializationSchema`.
    
    I tried to make this change not API breaking.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmetzger/flink kafka_kv

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1385.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1385
    
----
commit f4709fe83c554a471a4f6df90c8e9f73781379e1
Author: Robert Metzger <[email protected]>
Date:   2015-11-19T14:41:01Z

    [FLINK-3045] Properly expose the key of a Kafka message

commit 671c3792354e75a61b48042dbcb4c41e13aaf518
Author: Robert Metzger <[email protected]>
Date:   2015-11-19T14:52:57Z

    wip

----


> Properly expose the key of a kafka message
> ------------------------------------------
>
>                 Key: FLINK-3045
>                 URL: https://issues.apache.org/jira/browse/FLINK-3045
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kafka Connector
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>            Priority: Critical
>
> Currently, the {{flink-kafka-connector}} is not properly exposing the message 
> key.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to