Page History

...

The overrides can be specified in the connector config by using the following prefixes

• `producer.override` override.` - Used for source connector's producer  & DLQ producer in the context of SinkConnector
• `consumer.override.override` ` - Used for Sink Connector
• `admin.override.override` ` - Used for DLQ topic create in Sink Connector ( The KIP will also allow DLQ settings to be specified in the worker using `admin` prefix to be consistent with producer & consumer)

The administrator could either specify the fully qualified class name of the ConnectorClientConfigPolicy implementation or an alias (the alias is computed to be the prefix  prefix on the interface name `ConnectorClientConfigPolicy` which is exactly how most of the existing connect plugins compute their alias).

...

• Constructing producer for WorkerSourceTask - invoke validate with all configs with "producer.override." prefix , ClientType=Producer, ConnectorType=Source  & override if no policy violation 
• Constructing admin client & producer for DeadLetterQueueReporter for the DLQ topic 
  • invoke validate with all configs with "producer.override." prefix , ClientType=Producer, ConnectorType=Sink  & override if no policy violation 
  • invoke validate with all configs with "admin.override." prefix , ClientType=Admin, ConnectorType=Sink  & override if no policy violation 
• Constructing consumer for WorkerSinkTask - invoke validate with all configs with "consumer.override." prefix , ClientType=Consumer, ConnectorType=Sink  & override if no policy violation 

...