Hi Greg, I actually just found the following comment on this PR for https://issues.apache.org/jira/browse/KAFKA-13809: https://github.com/apache/kafka/pull/12450 > we get the same behavior (KAFKA-9228 notwithstanding) by passing the original >properties through to tasks transparently It seems we're not the first to notice that the issue isn't limited to connectors who selectively propagate properties to the task configs.FWIW, the kafka-connect-s3 connector also does not seem to prune any configs from the tasks: https://github.com/confluentinc/kafka-connect-storage-cloud/blob/d21662e78286d79b938e7b9affa418b863a6299f/kafka-connect-s3/src/main/java/io/confluent/connect/s3/S3SinkConnector.java#L57-L77 Is the patch provided on https://github.com/apache/kafka/pull/7823 still the right approach? Thanks!
- Kafka Connect ClusterConfigState.inconsistentConnectors() not... Frank Grimes
- Re: Kafka Connect ClusterConfigState.inconsistentConnect... Greg Harris
- Re: Kafka Connect ClusterConfigState.inconsistentCon... Greg Harris
- Re: Kafka Connect ClusterConfigState.inconsisten... Frank Grimes
- Re: Kafka Connect ClusterConfigState.inconsi... Greg Harris
- Re: Kafka Connect ClusterConfigState.in... Frank Grimes
- Re: Kafka Connect ClusterConfigStat... Greg Harris
- Re: Kafka Connect ClusterConfig... Frank Grimes
- Re: Kafka Connect ClusterConfig... Frank Grimes
- Re: Kafka Connect ClusterConfig... Greg Harris
- Re: Kafka Connect ClusterConfig... Frank Grimes
- Re: Kafka Connect ClusterConfig... Greg Harris
- Re: Kafka Connect ClusterConfig... Frank Grimes
- Re: Kafka Connect ClusterConfig... Frank Grimes
- Re: Kafka Connect ClusterConfig... Greg Harris
- Re: Kafka Connect ClusterConfig... Frank Grimes