[
https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297745#comment-15297745
]
Greg Fodor commented on KAFKA-3745:
-----------------------------------
Actually this seems like a good enough solution, I forgot to consider that the
stream still has the join key as it's key so I can grab it in a subsequent map.
All things considered this seems like a small price to pay for this rare case
vs introducing the parameter into the joiner interface, so I'm fine with
closing this ticket.
> 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)
