You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/06/23 16:45:00 UTC

[jira] [Commented] (KAFKA-5379) ProcessorContext.appConfigs() should return parsed/validated values

    [ https://issues.apache.org/jira/browse/KAFKA-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061203#comment-16061203 ] 

Guozhang Wang commented on KAFKA-5379:
--------------------------------------

[~twbecker] Could we make a pass over all the Type.CLASS configs in StreamsConfig and make sure users can either pass in a class name (for this case we should document that users any customized class with external dependency will not be supported as we are only relying on reflections) or class object, and the {{appConfigs}} can return the parsed objects as always in this JIRA?

Also note that we are adding a few more class typed configs cc [~enothereska] for serialization exception handler, we need to do the same for them.

> 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
>
> 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)