From 19d30fc8fecbb0d70f6125ef020e2ecbcdf67ac2 Mon Sep 17 00:00:00 2001
From: Hossein Torabi <hossein.torabi@alopeyk.com>
Date: Sat, 15 Feb 2020 16:56:21 +0330
Subject: [PATCH 1/2] [KAFKA-9563] Fix Kafka connect consumer and producer
 override documentation

---
 docs/connect.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/connect.html b/docs/connect.html
index a92bb04849fa1..b2536eceadb14 100644
--- a/docs/connect.html
+++ b/docs/connect.html
@@ -56,7 +56,7 @@ <h4><a id="connect_running" href="#connect_running">Running Kafka Connect</a></h
         <li><code>offset.storage.file.filename</code> - File to store offset data in</li>
     </ul>
 
-    <p>The parameters that are configured here are intended for producers and consumers used by Kafka Connect to access the configuration, offset and status topics. For configuration of Kafka source and Kafka sink tasks, the same parameters can be used but need to be prefixed with <code>consumer.</code> and <code>producer.</code> respectively. The only parameter that is inherited from the worker configuration is <code>bootstrap.servers</code>, which in most cases will be sufficient, since the same cluster is often used for all purposes. A notable exception is a secured cluster, which requires extra parameters to allow connections. These parameters will need to be set up to three times in the worker configuration, once for management access, once for Kafka sinks and once for Kafka sources.</p>
+    <p>The parameters that are configured here are intended for producers and consumers used by Kafka Connect to access the configuration, offset and status topics. For configuration of Kafka source and Kafka sink tasks, the same parameters can be used but need to be prefixed with <code>consumer.override.</code> and <code>producer.override.</code> respectively. The only parameter that is inherited from the worker configuration is <code>bootstrap.servers</code>, which in most cases will be sufficient, since the same cluster is often used for all purposes. A notable exception is a secured cluster, which requires extra parameters to allow connections. These parameters will need to be set up to three times in the worker configuration, once for management access, once for Kafka sinks and once for Kafka sources.</p>
 
     <p>The remaining parameters are connector configuration files. You may include as many as you want, but all will execute within the same process (on different threads).</p>
 

From 3a8d82e1515838ae6aaa7705692c532ae6905310 Mon Sep 17 00:00:00 2001
From: Hossein Torabi <blcksrx@gmail.com>
Date: Sun, 22 Mar 2020 19:55:10 +0430
Subject: [PATCH 2/2] Fix Kafka connect consumer and producer docs

Co-Authored-By: Konstantine Karantasis <konstantine@confluent.io>
---
 docs/connect.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/connect.html b/docs/connect.html
index b2536eceadb14..8101da9792b09 100644
--- a/docs/connect.html
+++ b/docs/connect.html
@@ -56,7 +56,9 @@ <h4><a id="connect_running" href="#connect_running">Running Kafka Connect</a></h
         <li><code>offset.storage.file.filename</code> - File to store offset data in</li>
     </ul>
 
-    <p>The parameters that are configured here are intended for producers and consumers used by Kafka Connect to access the configuration, offset and status topics. For configuration of Kafka source and Kafka sink tasks, the same parameters can be used but need to be prefixed with <code>consumer.override.</code> and <code>producer.override.</code> respectively. The only parameter that is inherited from the worker configuration is <code>bootstrap.servers</code>, which in most cases will be sufficient, since the same cluster is often used for all purposes. A notable exception is a secured cluster, which requires extra parameters to allow connections. These parameters will need to be set up to three times in the worker configuration, once for management access, once for Kafka sinks and once for Kafka sources.</p>
+    <p>The parameters that are configured here are intended for producers and consumers used by Kafka Connect to access the configuration, offset and status topics. For configuration of the producers used by Kafka source tasks and the consumers used by Kafka sink tasks, the same parameters can be used but need to be prefixed with <code>producer.</code> and <code>consumer.</code> respectively. The only Kafka client parameter that is inherited without a prefix from the worker configuration is <code>bootstrap.servers</code>, which in most cases will be sufficient, since the same cluster is often used for all purposes. A notable exception is a secured cluster, which requires extra parameters to allow connections. These parameters will need to be set up to three times in the worker configuration, once for management access, once for Kafka sources and once for Kafka sinks.</p> 
+    
+    <p>Starting with 2.3.0, client configuration overrides can be configured individually per connector by using the prefixes <code>producer.override.</code> and <code>consumer.override.</code> for Kafka sources or Kafka sinks respectively. These overrides are included with the rest of the connector's configuration properties.</p>
 
     <p>The remaining parameters are connector configuration files. You may include as many as you want, but all will execute within the same process (on different threads).</p>