kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3745) Consider adding join key to ValueJoiner interface
Date Mon, 09 Jan 2017 16:58:58 GMT

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

Matthias J. Sax commented on KAFKA-3745:

[~sree2k] thanks for picking this up. Just wanted to point out, as this JIRA contains a public
API change, you will need to write a KIP: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

> Consider adding join key to ValueJoiner interface
> -------------------------------------------------
>                 Key: KAFKA-3745
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3745
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions:
>            Reporter: Greg Fodor
>            Assignee: Sreepathi Prasanna
>            Priority: Minor
>              Labels: api, needs-kip, newbie
> In working with Kafka Stream joining, it's sometimes the case that a join key is not
actually present in the values of the joins themselves (if, for example, a previous transform
generated an ephemeral join key.) In such cases, the actual key of the join is not available
in the ValueJoiner implementation to be used to construct the final joined value. This can
be worked around by explicitly threading the join key into the value if needed, but it seems
like extending the interface to pass the join key along as well would be helpful.

This message was sent by Atlassian JIRA

View raw message