[
https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990294#comment-15990294
]
ASF GitHub Bot commented on KAFKA-4218:
---------------------------------------
GitHub user jeyhunkarimov opened a pull request:
https://github.com/apache/kafka/pull/2946
KAFKA-4218: Enable access to key in ValueTransformer
This PR groups KAFKA-4218, KAFKA-4726 and KAFKA-3745.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jeyhunkarimov/kafka KAFKA-4218
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2946.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 #2946
----
commit f535f8ea126a34e2854ed45e9131324099c7aa71
Author: Jeyhun Karimov <je.kari...@gmail.com>
Date: 2017-04-30T16:11:57Z
KAFKA-4218
bug fix in KTableImplTest
----
> Enable access to key in ValueTransformer
> ----------------------------------------
>
> Key: KAFKA-4218
> URL: https://issues.apache.org/jira/browse/KAFKA-4218
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.0.1
> Reporter: Elias Levy
> Assignee: Jeyhun Karimov
> Labels: api, needs-kip, newbie
>
> While transforming values via {{KStream.transformValues}} and
> {{ValueTransformer}}, the key associated with the value may be needed, even
> if it is not changed. For instance, it may be used to access stores.
> As of now, the key is not available within these methods and interfaces,
> leading to the use of {{KStream.transform}} and {{Transformer}}, and the
> unnecessary creation of new {{KeyValue}} objects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
