Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Mon, 23 May 2016 16:27:13 +0000 (UTC)
From: "Guozhang Wang (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12971933.1463975767000.267196.1464020833114@Atlassian.JIRA>
In-Reply-To: <JIRA.12971933.1463975767000@Atlassian.JIRA>
References: <JIRA.12971933.1463975767000@Atlassian.JIRA> <JIRA.12971933.1463975767279@arcas>
Subject: [jira] [Updated] (KAFKA-3745) Consider adding join key to
 ValueJoiner interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 23 May 2016 16:27:17 -0000


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

Guozhang Wang updated KAFKA-3745:
---------------------------------
    Labels: api newbie  (was: api)

> 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: 0.10.0.0
>            Reporter: Greg Fodor
>            Priority: Minor
>              Labels: api, 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
(v6.3.4#6332)