You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2019/04/01 15:30:00 UTC

[jira] [Commented] (KAFKA-7588) Rationalize configurations passed to pluggable APIs

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

Rajini Sivaram commented on KAFKA-7588:
---------------------------------------

[~mimaison] Are you planning to submit a PR for this? I was interested in custom configs in callback handlers, but as you said, it will be good to do this consistently for all configurables. Thanks.

> Rationalize configurations passed to pluggable APIs
> ---------------------------------------------------
>
>                 Key: KAFKA-7588
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7588
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Mickael Maison
>            Assignee: Mickael Maison
>            Priority: Major
>
> There are a lot of extensions points both on the client and server sides. Most of these pluggable APIs are configurable but the configurations they receive are not the same.
> For example, Serializers, Deserializers, Partitioners, Assignors, QuotaCallbacks are passed config.originals(). On the other hand LoginModules, PrincipalBuilders and AuthenticationCallbackHandlers are passed config.values().
> In practice, having access to originals() is nice as it allows to use custom configurations by simply adding it to the client/server configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)