Chris Egerton created KAFKA-12717:
-------------------------------------
Summary: Remove internal converter config properties
Key: KAFKA-12717
URL: https://issues.apache.org/jira/browse/KAFKA-12717
Project: Kafka
Issue Type: Bug
Components: KafkaConnect
Reporter: Chris Egerton
Assignee: Chris Egerton
KAFKA-5540 /
[KIP-174|https://cwiki.apache.org/confluence/display/KAFKA/KIP-174+-+Deprecate+and+remove+internal+converter+configs+in+WorkerConfig]
deprecated but did not officially remove Connect's internal converter worker
config properties. With the upcoming 3.0 release, we can make the
backwards-incompatible change of completely removing these properties once and
for all.
One migration path for users who may still be running Connect clusters with
different internal converters can be:
# Stop all workers on the cluster
# For each internal topic (config, offsets, and status):
## Create a new topic to take the place of the existing one
## For every message in the existing topic:
### Deserialize the message's key and value using the Connect cluster's old
internal key and value converters
### Serialize the message's key and value using the [JSON
converter|https://github.com/apache/kafka/blob/trunk/connect/json/src/main/java/org/apache/kafka/connect/json/JsonConverter.java]
with schemas disabled (by setting the {{schemas.enable}} property to {{false}})
### Write a message with the new key and value to the new internal topic
# Reconfigure each Connect worker to use the newly-created internal topics
from step 2
# Start all workers on the cluster
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
