You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/29 01:49:00 UTC

[jira] [Commented] (KAFKA-5538) User-specified Producer/Consumer config doesn't effect with KafkaBackingStore(Config/Status/Offset)

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

ASF GitHub Bot commented on KAFKA-5538:
---------------------------------------

kkonstantine commented on pull request #3458: KAFKA-5538: User-specified Producer/Consumer config doesn't effect wi…
URL: https://github.com/apache/kafka/pull/3458
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> User-specified Producer/Consumer config doesn't effect with KafkaBackingStore(Config/Status/Offset)
> ---------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5538
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5538
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.11.0.0
>            Reporter: Aegeaner
>            Assignee: Aegeaner
>            Priority: Major
>
> For configuration of Kafka source and Kafka sink tasks, the same parameters can be used but need to be prefixed with consumer. and producer. The worker will take off the prefix and get user specified configurations, but the KafkaBackingStores will not. All the three KafkaBackingStores just took originals from the Kafka config without taking off the prefix, so the producer/consumer will ignore these configurations. (e.g. Kerberos configs)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)