[
https://issues.apache.org/jira/browse/KAFKA-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146165#comment-16146165
]
ASF GitHub Bot commented on KAFKA-5379:
---------------------------------------
GitHub user guozhangwang opened a pull request:
https://github.com/apache/kafka/pull/3757
KAFKA-5379 follow up: reduce redundant mock processor context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/guozhangwang/kafka K5379-follow-up
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3757.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 #3757
----
commit c750932d05559c3e7d28c64a1a334db680cfe77f
Author: Guozhang Wang <wangg...@gmail.com>
Date: 2017-08-29T20:59:44Z
remove two test processor context into mock processor context
commit d2fc3853ff3caa6f10e9932e90b995ff5a4807ea
Author: Guozhang Wang <wangg...@gmail.com>
Date: 2017-08-29T21:27:28Z
some reverts
----
> ProcessorContext.appConfigs() should return parsed/validated values
> -------------------------------------------------------------------
>
> Key: KAFKA-5379
> URL: https://issues.apache.org/jira/browse/KAFKA-5379
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.2.1
> Reporter: Tommy Becker
> Assignee: Tommy Becker
> Priority: Minor
> Fix For: 1.0.0
>
>
> As part of KAFKA-5334, it was decided that the current behavior of
> {{ProcessorContext.appConfigs()}} is sub-optimal in that it returns the
> original unparsed config values. Alternatively, the parsed values could be
> returned which would allow callers to know what they are getting as well
> avoid duplicating type conversions (e.g. className -> class).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
