GitHub user backender opened a pull request:
https://github.com/apache/kafka/pull/2703
KAFKA-4772: Use peek to implement print
**Tackles [KAFKA-4772](https://issues.apache.org/jira/browse/KAFKA-4772)
and was previously discussed in https://github.com/apache/kafka/pull/2669**
The functionality of `KeyValuePrinter` is replaced with `PrintAction` which
implements `ForeachAction` and can be passed to `KStreamPeek`. We therefore can
get rid of `KeyValuePrinter`.
My only concern is that `ForeachAction` does not have access to the
`ProcessorContext`, which means, that the topic name cannot be used within the
deserialization process. For now, the a null value is filled in as a
placeholder for topic.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/delftswa2017/kafka fix-KAFKA-4772-notopic
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2703.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 #2703
----
commit 46d5f20eb1ee69abc24b05f890eca620d2399b17
Author: Marc Juchli <m...@marcjuch.li>
Date: 2017-03-18T14:00:59Z
Use peek to implement print
The functionaliy of KeyValuePrinter is replaced with PrintAction which
implements ForeachAction and can be passed to KStreamPeek.
We therefore can get rid of KeyValuePrinter.
My only concern is that ForeachAction does not have access to the
ProcessorContext, which means, that the topic name cannot be used within
the deserialization process.
For now, the a null value is filled in as a placeholder for topic.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
