kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams
Date Thu, 01 Jun 2017 22:06:04 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033793#comment-16033793

ASF GitHub Bot commented on KAFKA-5311:

GitHub user subnova opened a pull request:


    KAFKA-5311: Support ExtendedDeserializer in Kafka Streams.

    The contribution is my original work and I license the work to the project under the project's
open source license.
    This is a clone of the previous PR #3125 but now against trunk.

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

    $ git pull https://github.com/subnova/kafka streams-extendeddeserializer

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


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

    This closes #3199
commit 32a75c6a3a072aceff88a87e381ad3e4b46d04f7
Author: Dale Peakall <dale@peakall.net>
Date:   2017-05-23T10:40:32Z

    KAFKA-5311: Support ExtendedDeserializer in Kafka Streams.
    Author: Dale Peakall <dale@peakall.net>


> Support ExtendedDeserializer in Kafka Streams
> ---------------------------------------------
>                 Key: KAFKA-5311
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5311
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions:
>            Reporter: Dale Peakall
>            Assignee: Dale Peakall
>             Fix For:
> KIP-82 introduced the concept of message headers and introduced an ExtendedDeserializer
interface that allowed a Deserializer to access those message headers.
> Change Kafka Streams to support the use of ExtendedDeserializer to provide compatibility
with Kafka Clients that use the new header functionality.

This message was sent by Atlassian JIRA

View raw message