...

JIRA:

...

• Purge repartition data on commit: this is summarized in 

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-6150

  . The AdminClient's deleteRecords API (adding in KIP-204) will be used upon committing intervals.
• Create internal topic within InternalTopicManager: we will use the create topic API to do that, and also we
• We'll also remove the endless-loop checking after the creation within StreamPartitionAssignor ; Instead (

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-6126

  ); instead after the rebalance we will let the restoration retry within the main loop if the metadata is not known yet.
• Compatibility check: we will use a network client for this purpose, as it is a one-time thing.

Regarding the changes to replace StreamsKafkaClient with the KafkaAdminClient, the only differences are the configs. Here is a list of configs defined in StreamsConfig that will be used in StreamsKafkaClient:

• StreamsConfig.CLIENT_ID_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.RETRY_BACKOFF_MS_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.METADATA_MAX_AGE_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.CONNECTIONS_MAX_IDLE_MS_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.RECONNECT_BACKOFF_MS_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.RECONNECT_BACKOFF_MAX_MS_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.SEND_BUFFER_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.RECEIVE_BUFFER_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.REQUEST_TIMEOUT_MS_CONFIG: still used in KafkaAdminClient.
• StreamsConfig.BOOTSTRAP_SERVERS_CONFIG: still used in KafkaAdminClient.
  

So none of the defined properties in StreamsConfig need to be deprecated or removed. No Changes here.

Compatibility, Deprecation, and Migration Plan

...