[
https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989730#comment-15989730
]
Matthias J. Sax edited comment on KAFKA-4218 at 4/29/17 3:32 AM:
-----------------------------------------------------------------
[~jeyhunkarimov], thanks for picking this up. I want to point out, that we have
many API tickets and that all of them make sense, but conflict with each other
sometimes with regard to a proposed solution. We collected an overview in the
wiki:
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams+Discussions
I point this out, as it does not make sense to work on a single JIRA in
isolation. We will need a general discussion how we want to resolve the
different JIRAs in an holistic way. Thus, if you want to work on this, please
look at all related JIRAs. It would make sense to "group" JIRAs and do one KIP
per group -- it's to be determined how to do the grouping though... I guess
it's up to you to make a first move and pick a group of JIRA's that make sense
to put together, a propose one holistic KIP that cover all of them at once. We
can take the discussion from there, after you started the DISCUSS thread on the
mailing list.
Does this make sense to you and is it ok for you to work this way?
was (Author: mjsax):
[~jeyhunkarimov], thanks for picking this up. I want to point out, that we have
many API tickets and that all of them make sense, but conflict with each other
sometimes with regard to a proposed solution. We collected an overview in the
wiki:
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams+Discussions
I point this out, as it does not make sense to work on a single JIRA in
isolation. We will need a general discussion how we want to resolve the
different JIRAs in an holistic way. Thus, if you want to work on this, please
look at all related JIRAs. It would make sense to "group" JIRAs and do one KIP
per group -- it's to be determined how to do the grouping though... I guess
it's up to you to make a first move and pick a group of JIRA's that make sense
to put togethre, a propose one holistic KIP that cover all of them at once. We
can take the discussion from there, after you started the DISCUSS thread on the
mailing list.
Does this make sense to you and is it ok for you to work this way?
> 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)
