You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by mi...@apache.org on 2025/08/28 14:11:20 UTC
(kafka-site) branch asf-site updated: MINOR: Add 4.1 docs (#702)
This is an automated email from the ASF dual-hosted git repository.
mimaison pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 8d0708cf3 MINOR: Add 4.1 docs (#702)
8d0708cf3 is described below
commit 8d0708cf3ceda61415e572f5b8536ba4ce6f4864
Author: Mickael Maison <mi...@users.noreply.github.com>
AuthorDate: Thu Aug 28 16:11:15 2025 +0200
MINOR: Add 4.1 docs (#702)
Reviewers: Luke Chen <sh...@gmail.com>
---
41/README.md | 4 +
41/api.html | 124 +
41/compatibility-summary.html | 27 +
41/configuration.html | 442 +
41/connect.html | 1056 +
41/design.html | 764 +
41/docker.html | 58 +
41/documentation.html | 124 +
41/documentation/compatibility.html | 201 +
41/documentation/index.html | 18 +
41/documentation/streams/architecture.html | 19 +
41/documentation/streams/core-concepts.html | 19 +
.../streams/developer-guide/app-reset-tool.html | 19 +
.../streams/developer-guide/config-streams.html | 19 +
.../streams/developer-guide/datatypes.html | 19 +
.../streams/developer-guide/dsl-api.html | 19 +
.../developer-guide/dsl-topology-naming.html | 19 +
.../streams/developer-guide/index.html | 19 +
.../developer-guide/interactive-queries.html | 19 +
.../streams/developer-guide/manage-topics.html | 19 +
.../streams/developer-guide/memory-mgmt.html | 19 +
.../streams/developer-guide/processor-api.html | 19 +
.../streams/developer-guide/running-app.html | 19 +
.../streams/developer-guide/security.html | 19 +
.../streams/developer-guide/testing.html | 19 +
.../streams/developer-guide/write-streams.html | 19 +
41/documentation/streams/index.html | 19 +
41/documentation/streams/quickstart.html | 19 +
41/documentation/streams/tutorial.html | 19 +
41/documentation/streams/upgrade-guide.html | 19 +
41/documentation/zk2kraft.html | 320 +
41/ecosystem.html | 18 +
41/generated/admin_client_config.html | 903 +
41/generated/connect_config.html | 1333 ++
41/generated/connect_metrics.html | 463 +
41/generated/connect_predicates.html | 45 +
41/generated/connect_rest.yaml | 715 +
41/generated/connect_transforms.html | 549 +
41/generated/consumer_config.html | 1133 +
41/generated/consumer_metrics.html | 153 +
.../directory_config_provider_configs.html | 13 +
41/generated/envvar_config_provider_configs.html | 13 +
41/generated/file_config_provider_configs.html | 13 +
41/generated/group_config.html | 103 +
41/generated/kafka_config.html | 3479 +++
41/generated/mirror_checkpoint_config.html | 133 +
41/generated/mirror_connector_config.html | 933 +
41/generated/mirror_heartbeat_config.html | 33 +
41/generated/mirror_source_config.html | 183 +
41/generated/producer_config.html | 1123 +
41/generated/producer_metrics.html | 163 +
41/generated/protocol_api_keys.html | 155 +
41/generated/protocol_errors.html | 143 +
41/generated/protocol_messages.html | 18692 +++++++++++++++
41/generated/protocol_types.html | 29 +
41/generated/remote_log_manager_config.html | 263 +
.../remote_log_metadata_manager_config.html | 63 +
41/generated/sink_connector_config.html | 243 +
41/generated/source_connector_config.html | 243 +
41/generated/streams_config.html | 683 +
41/generated/topic_config.html | 366 +
41/images/consumer-groups.png | Bin 0 -> 26820 bytes
41/images/creating-streams-iframe-placeholder.png | Bin 0 -> 54371 bytes
41/images/icons/NYT.jpg | Bin 0 -> 12605 bytes
41/images/icons/architecture--white.png | Bin 0 -> 812 bytes
41/images/icons/architecture.png | Bin 0 -> 818 bytes
41/images/icons/documentation--white.png | Bin 0 -> 1758 bytes
41/images/icons/documentation.png | Bin 0 -> 1642 bytes
41/images/icons/line.png | Bin 0 -> 676 bytes
41/images/icons/new-york.png | Bin 0 -> 3381 bytes
41/images/icons/rabobank.png | Bin 0 -> 3593 bytes
41/images/icons/tutorials--white.png | Bin 0 -> 1047 bytes
41/images/icons/tutorials.png | Bin 0 -> 985 bytes
41/images/icons/zalando.png | Bin 0 -> 2716 bytes
41/images/intro_to_streams-iframe-placeholder.png | Bin 0 -> 40352 bytes
41/images/kafka-apis.png | Bin 0 -> 86640 bytes
41/images/kafka-logo-readme-dark.svg | 217 +
41/images/kafka-logo-readme-light.svg | 217 +
41/images/kafka_log.png | Bin 0 -> 114789 bytes
41/images/kafka_multidc.png | Bin 0 -> 33959 bytes
41/images/kafka_multidc_complex.png | Bin 0 -> 38559 bytes
41/images/log_anatomy.png | Bin 0 -> 19579 bytes
41/images/log_cleaner_anatomy.png | Bin 0 -> 18638 bytes
41/images/log_compaction.png | Bin 0 -> 41414 bytes
41/images/log_consumer.png | Bin 0 -> 139658 bytes
41/images/mirror-maker.png | Bin 0 -> 6579 bytes
41/images/producer_consumer.png | Bin 0 -> 8691 bytes
41/images/streams-architecture-overview.jpg | Bin 0 -> 420929 bytes
41/images/streams-architecture-states.jpg | Bin 0 -> 147338 bytes
41/images/streams-architecture-tasks.jpg | Bin 0 -> 130435 bytes
41/images/streams-architecture-threads.jpg | Bin 0 -> 153622 bytes
41/images/streams-architecture-topology.jpg | Bin 0 -> 182199 bytes
41/images/streams-cache-and-commit-interval.png | Bin 0 -> 38648 bytes
41/images/streams-concepts-topology.jpg | Bin 0 -> 136983 bytes
41/images/streams-elastic-scaling-1.png | Bin 0 -> 88673 bytes
41/images/streams-elastic-scaling-2.png | Bin 0 -> 91141 bytes
41/images/streams-elastic-scaling-3.png | Bin 0 -> 88604 bytes
41/images/streams-interactive-queries-01.png | Bin 0 -> 80976 bytes
41/images/streams-interactive-queries-02.png | Bin 0 -> 73218 bytes
41/images/streams-interactive-queries-03.png | Bin 0 -> 79879 bytes
41/images/streams-interactive-queries-api-01.png | Bin 0 -> 84438 bytes
41/images/streams-interactive-queries-api-02.png | Bin 0 -> 100725 bytes
41/images/streams-session-windows-01.png | Bin 0 -> 49003 bytes
41/images/streams-session-windows-02.png | Bin 0 -> 55956 bytes
41/images/streams-sliding-windows.png | Bin 0 -> 38991 bytes
41/images/streams-stateful_operations.png | Bin 0 -> 123213 bytes
41/images/streams-table-duality-01.png | Bin 0 -> 14534 bytes
41/images/streams-table-duality-02.png | Bin 0 -> 56736 bytes
41/images/streams-table-duality-03.png | Bin 0 -> 91331 bytes
41/images/streams-table-updates-01.png | Bin 0 -> 78069 bytes
41/images/streams-table-updates-02.png | Bin 0 -> 91880 bytes
41/images/streams-time-windows-hopping.png | Bin 0 -> 110392 bytes
41/images/streams-time-windows-tumbling.png | Bin 0 -> 63888 bytes
41/images/streams-welcome.png | Bin 0 -> 80530 bytes
41/images/tracking_high_level.png | Bin 0 -> 82759 bytes
.../transforming_part_1-iframe-placeholder.png | Bin 0 -> 47515 bytes
.../transforming_part_2-iframe-placeholder.png | Bin 0 -> 43720 bytes
41/implementation.html | 201 +
41/introduction.html | 220 +
41/javadoc/allclasses-index.html | 3862 +++
41/javadoc/allpackages-index.html | 275 +
41/javadoc/constant-values.html | 2368 ++
41/javadoc/deprecated-list.html | 506 +
41/javadoc/element-list | 53 +
41/javadoc/help-doc.html | 191 +
41/javadoc/index-all.html | 23433 +++++++++++++++++++
41/javadoc/index.html | 277 +
41/javadoc/jquery-ui.overrides.css | 35 +
41/javadoc/legal/ADDITIONAL_LICENSE_INFO | 37 +
41/javadoc/legal/ASSEMBLY_EXCEPTION | 27 +
41/javadoc/legal/LICENSE | 347 +
41/javadoc/legal/jquery.md | 26 +
41/javadoc/legal/jqueryUI.md | 49 +
41/javadoc/member-search-index.js | 1 +
41/javadoc/module-search-index.js | 1 +
.../clients/admin/AbortTransactionOptions.html | 167 +
.../clients/admin/AbortTransactionResult.html | 143 +
.../kafka/clients/admin/AbortTransactionSpec.html | 230 +
.../kafka/clients/admin/AbstractOptions.html | 181 +
.../kafka/clients/admin/AddRaftVoterOptions.html | 174 +
.../kafka/clients/admin/AddRaftVoterResult.html | 138 +
.../org/apache/kafka/clients/admin/Admin.html | 3521 +++
.../apache/kafka/clients/admin/AdminClient.html | 202 +
.../kafka/clients/admin/AdminClientConfig.html | 797 +
.../clients/admin/AlterClientQuotasOptions.html | 179 +
.../clients/admin/AlterClientQuotasResult.html | 181 +
.../kafka/clients/admin/AlterConfigOp.OpType.html | 274 +
.../apache/kafka/clients/admin/AlterConfigOp.html | 224 +
.../kafka/clients/admin/AlterConfigsOptions.html | 197 +
.../kafka/clients/admin/AlterConfigsResult.html | 147 +
.../admin/AlterConsumerGroupOffsetsOptions.html | 133 +
.../admin/AlterConsumerGroupOffsetsResult.html | 147 +
.../admin/AlterPartitionReassignmentsOptions.html | 185 +
.../admin/AlterPartitionReassignmentsResult.html | 153 +
.../clients/admin/AlterReplicaLogDirsOptions.html | 133 +
.../clients/admin/AlterReplicaLogDirsResult.html | 171 +
.../admin/AlterShareGroupOffsetsOptions.html | 136 +
.../admin/AlterShareGroupOffsetsResult.html | 150 +
.../admin/AlterStreamsGroupOffsetsOptions.html | 136 +
.../admin/AlterStreamsGroupOffsetsResult.html | 150 +
.../admin/AlterUserScramCredentialsOptions.html | 133 +
.../admin/AlterUserScramCredentialsResult.html | 181 +
.../clients/admin/ClassicGroupDescription.html | 317 +
.../admin/ClientMetricsResourceListing.html | 214 +
.../org/apache/kafka/clients/admin/Config.html | 217 +
.../clients/admin/ConfigEntry.ConfigSource.html | 278 +
.../clients/admin/ConfigEntry.ConfigSynonym.html | 202 +
.../clients/admin/ConfigEntry.ConfigType.html | 286 +
.../apache/kafka/clients/admin/ConfigEntry.html | 376 +
.../clients/admin/ConsumerGroupDescription.html | 434 +
.../kafka/clients/admin/ConsumerGroupListing.html | 398 +
.../kafka/clients/admin/CreateAclsOptions.html | 173 +
.../kafka/clients/admin/CreateAclsResult.html | 149 +
.../admin/CreateDelegationTokenOptions.html | 243 +
.../clients/admin/CreateDelegationTokenResult.html | 135 +
.../clients/admin/CreatePartitionsOptions.html | 203 +
.../clients/admin/CreatePartitionsResult.html | 149 +
.../kafka/clients/admin/CreateTopicsOptions.html | 221 +
.../CreateTopicsResult.TopicMetadataAndConfig.html | 203 +
.../kafka/clients/admin/CreateTopicsResult.html | 237 +
.../kafka/clients/admin/DeleteAclsOptions.html | 173 +
.../admin/DeleteAclsResult.FilterResult.html | 151 +
.../admin/DeleteAclsResult.FilterResults.html | 139 +
.../kafka/clients/admin/DeleteAclsResult.html | 172 +
.../admin/DeleteConsumerGroupOffsetsOptions.html | 133 +
.../admin/DeleteConsumerGroupOffsetsResult.html | 148 +
.../clients/admin/DeleteConsumerGroupsOptions.html | 133 +
.../clients/admin/DeleteConsumerGroupsResult.html | 149 +
.../kafka/clients/admin/DeleteRecordsOptions.html | 133 +
.../kafka/clients/admin/DeleteRecordsResult.html | 176 +
.../admin/DeleteShareGroupOffsetsOptions.html | 136 +
.../admin/DeleteShareGroupOffsetsResult.html | 151 +
.../clients/admin/DeleteShareGroupsOptions.html | 136 +
.../clients/admin/DeleteShareGroupsResult.html | 152 +
.../admin/DeleteStreamsGroupOffsetsOptions.html | 136 +
.../admin/DeleteStreamsGroupOffsetsResult.html | 150 +
.../clients/admin/DeleteStreamsGroupsOptions.html | 136 +
.../clients/admin/DeleteStreamsGroupsResult.html | 150 +
.../kafka/clients/admin/DeleteTopicsOptions.html | 197 +
.../kafka/clients/admin/DeleteTopicsResult.html | 170 +
.../apache/kafka/clients/admin/DeletedRecords.html | 169 +
.../kafka/clients/admin/DescribeAclsOptions.html | 173 +
.../kafka/clients/admin/DescribeAclsResult.html | 135 +
.../admin/DescribeClassicGroupsOptions.html | 176 +
.../clients/admin/DescribeClassicGroupsResult.html | 177 +
.../clients/admin/DescribeClientQuotasOptions.html | 133 +
.../clients/admin/DescribeClientQuotasResult.html | 170 +
.../clients/admin/DescribeClusterOptions.html | 217 +
.../kafka/clients/admin/DescribeClusterResult.html | 175 +
.../clients/admin/DescribeConfigsOptions.html | 221 +
.../kafka/clients/admin/DescribeConfigsResult.html | 149 +
.../admin/DescribeConsumerGroupsOptions.html | 174 +
.../admin/DescribeConsumerGroupsResult.html | 174 +
.../admin/DescribeDelegationTokenOptions.html | 184 +
.../admin/DescribeDelegationTokenResult.html | 135 +
.../clients/admin/DescribeFeaturesOptions.html | 133 +
.../clients/admin/DescribeFeaturesResult.html | 134 +
.../clients/admin/DescribeLogDirsOptions.html | 133 +
.../kafka/clients/admin/DescribeLogDirsResult.html | 150 +
.../admin/DescribeMetadataQuorumOptions.html | 133 +
.../admin/DescribeMetadataQuorumResult.html | 135 +
.../clients/admin/DescribeProducersOptions.html | 212 +
...ribeProducersResult.PartitionProducerState.html | 175 +
.../clients/admin/DescribeProducersResult.html | 155 +
.../admin/DescribeReplicaLogDirsOptions.html | 133 +
...ribeReplicaLogDirsResult.ReplicaLogDirInfo.html | 190 +
.../admin/DescribeReplicaLogDirsResult.html | 162 +
.../clients/admin/DescribeShareGroupsOptions.html | 176 +
.../clients/admin/DescribeShareGroupsResult.html | 177 +
.../admin/DescribeStreamsGroupsOptions.html | 176 +
.../clients/admin/DescribeStreamsGroupsResult.html | 177 +
.../kafka/clients/admin/DescribeTopicsOptions.html | 224 +
.../kafka/clients/admin/DescribeTopicsResult.html | 189 +
.../clients/admin/DescribeTransactionsOptions.html | 168 +
.../clients/admin/DescribeTransactionsResult.html | 166 +
.../admin/DescribeUserScramCredentialsOptions.html | 133 +
.../admin/DescribeUserScramCredentialsResult.html | 175 +
.../kafka/clients/admin/ElectLeadersOptions.html | 135 +
.../kafka/clients/admin/ElectLeadersResult.html | 151 +
.../apache/kafka/clients/admin/EndpointType.html | 244 +
.../admin/ExpireDelegationTokenOptions.html | 179 +
.../clients/admin/ExpireDelegationTokenResult.html | 135 +
.../kafka/clients/admin/FeatureMetadata.html | 204 +
.../clients/admin/FeatureUpdate.UpgradeType.html | 255 +
.../apache/kafka/clients/admin/FeatureUpdate.html | 235 +
.../kafka/clients/admin/FenceProducersOptions.html | 168 +
.../kafka/clients/admin/FenceProducersResult.html | 173 +
.../kafka/clients/admin/FinalizedVersionRange.html | 221 +
.../kafka/clients/admin/ForwardingAdmin.html | 2148 ++
.../apache/kafka/clients/admin/GroupListing.html | 291 +
.../kafka/clients/admin/KafkaAdminClient.html | 1996 ++
.../admin/ListClientMetricsResourcesOptions.html | 140 +
.../admin/ListClientMetricsResourcesResult.html | 147 +
.../clients/admin/ListConfigResourcesOptions.html | 133 +
.../clients/admin/ListConfigResourcesResult.html | 139 +
.../admin/ListConsumerGroupOffsetsOptions.html | 177 +
.../admin/ListConsumerGroupOffsetsResult.html | 167 +
.../admin/ListConsumerGroupOffsetsSpec.html | 221 +
.../clients/admin/ListConsumerGroupsOptions.html | 259 +
.../clients/admin/ListConsumerGroupsResult.html | 186 +
.../kafka/clients/admin/ListGroupsOptions.html | 273 +
.../kafka/clients/admin/ListGroupsResult.html | 177 +
.../kafka/clients/admin/ListOffsetsOptions.html | 172 +
.../ListOffsetsResult.ListOffsetsResultInfo.html | 197 +
.../kafka/clients/admin/ListOffsetsResult.html | 191 +
.../admin/ListPartitionReassignmentsOptions.html | 133 +
.../admin/ListPartitionReassignmentsResult.html | 137 +
.../admin/ListShareGroupOffsetsOptions.html | 136 +
.../clients/admin/ListShareGroupOffsetsResult.html | 155 +
.../clients/admin/ListShareGroupOffsetsSpec.html | 221 +
.../admin/ListStreamsGroupOffsetsOptions.html | 179 +
.../admin/ListStreamsGroupOffsetsResult.html | 151 +
.../clients/admin/ListStreamsGroupOffsetsSpec.html | 131 +
.../kafka/clients/admin/ListTopicsOptions.html | 243 +
.../kafka/clients/admin/ListTopicsResult.html | 159 +
.../clients/admin/ListTransactionsOptions.html | 341 +
.../clients/admin/ListTransactionsResult.html | 185 +
.../kafka/clients/admin/LogDirDescription.html | 235 +
.../kafka/clients/admin/MemberAssignment.html | 208 +
.../kafka/clients/admin/MemberDescription.html | 377 +
.../apache/kafka/clients/admin/MemberToRemove.html | 185 +
.../clients/admin/NewPartitionReassignment.html | 163 +
.../apache/kafka/clients/admin/NewPartitions.html | 215 +
.../org/apache/kafka/clients/admin/NewTopic.html | 314 +
.../admin/OffsetSpec.EarliestLocalSpec.html | 145 +
.../clients/admin/OffsetSpec.EarliestSpec.html | 145 +
.../kafka/clients/admin/OffsetSpec.LatestSpec.html | 145 +
.../clients/admin/OffsetSpec.LatestTieredSpec.html | 145 +
.../clients/admin/OffsetSpec.MaxTimestampSpec.html | 145 +
.../clients/admin/OffsetSpec.TimestampSpec.html | 114 +
.../org/apache/kafka/clients/admin/OffsetSpec.html | 272 +
.../kafka/clients/admin/PartitionReassignment.html | 205 +
.../apache/kafka/clients/admin/ProducerState.html | 252 +
.../kafka/clients/admin/QuorumInfo.Node.html | 183 +
.../clients/admin/QuorumInfo.ReplicaState.html | 245 +
.../org/apache/kafka/clients/admin/QuorumInfo.html | 238 +
.../kafka/clients/admin/RaftVoterEndpoint.html | 251 +
.../kafka/clients/admin/RecordsToDelete.html | 190 +
.../RemoveMembersFromConsumerGroupOptions.html | 203 +
.../RemoveMembersFromConsumerGroupResult.html | 151 +
.../clients/admin/RemoveRaftVoterOptions.html | 174 +
.../kafka/clients/admin/RemoveRaftVoterResult.html | 138 +
.../clients/admin/RenewDelegationTokenOptions.html | 173 +
.../clients/admin/RenewDelegationTokenResult.html | 135 +
.../apache/kafka/clients/admin/ReplicaInfo.html | 216 +
.../kafka/clients/admin/ScramCredentialInfo.html | 230 +
.../apache/kafka/clients/admin/ScramMechanism.html | 309 +
.../kafka/clients/admin/ShareGroupDescription.html | 304 +
.../kafka/clients/admin/ShareMemberAssignment.html | 209 +
.../clients/admin/ShareMemberDescription.html | 258 +
.../clients/admin/StreamsGroupDescription.html | 314 +
.../StreamsGroupMemberAssignment.TaskIds.html | 219 +
.../admin/StreamsGroupMemberAssignment.html | 247 +
.../StreamsGroupMemberDescription.Endpoint.html | 213 +
.../StreamsGroupMemberDescription.TaskOffset.html | 233 +
.../admin/StreamsGroupMemberDescription.html | 420 +
...reamsGroupSubtopologyDescription.TopicInfo.html | 234 +
.../admin/StreamsGroupSubtopologyDescription.html | 275 +
.../kafka/clients/admin/SupportedVersionRange.html | 221 +
.../clients/admin/TerminateTransactionOptions.html | 168 +
.../clients/admin/TerminateTransactionResult.html | 135 +
.../kafka/clients/admin/TopicDescription.html | 316 +
.../apache/kafka/clients/admin/TopicListing.html | 213 +
.../clients/admin/TransactionDescription.html | 263 +
.../kafka/clients/admin/TransactionListing.html | 219 +
.../kafka/clients/admin/TransactionState.html | 287 +
.../clients/admin/UnregisterBrokerOptions.html | 133 +
.../clients/admin/UnregisterBrokerResult.html | 137 +
.../kafka/clients/admin/UpdateFeaturesOptions.html | 173 +
.../kafka/clients/admin/UpdateFeaturesResult.html | 146 +
.../admin/UserScramCredentialAlteration.html | 148 +
.../clients/admin/UserScramCredentialDeletion.html | 183 +
.../admin/UserScramCredentialUpsertion.html | 260 +
.../admin/UserScramCredentialsDescription.html | 231 +
.../kafka/clients/admin/package-summary.html | 841 +
.../apache/kafka/clients/admin/package-tree.html | 307 +
.../kafka/clients/consumer/AcknowledgeType.html | 288 +
.../consumer/AcknowledgementCommitCallback.html | 149 +
.../CloseOptions.GroupMembershipOperation.html | 241 +
.../kafka/clients/consumer/CloseOptions.html | 230 +
.../clients/consumer/CommitFailedException.html | 162 +
.../apache/kafka/clients/consumer/Consumer.html | 1029 +
.../kafka/clients/consumer/ConsumerConfig.html | 1454 ++
.../clients/consumer/ConsumerGroupMetadata.html | 240 +
.../clients/consumer/ConsumerInterceptor.html | 211 +
.../ConsumerPartitionAssignor.Assignment.html | 194 +
.../ConsumerPartitionAssignor.GroupAssignment.html | 175 +
...onsumerPartitionAssignor.GroupSubscription.html | 175 +
...onsumerPartitionAssignor.RebalanceProtocol.html | 254 +
.../ConsumerPartitionAssignor.Subscription.html | 267 +
.../consumer/ConsumerPartitionAssignor.html | 284 +
.../consumer/ConsumerRebalanceListener.html | 318 +
.../kafka/clients/consumer/ConsumerRecord.html | 508 +
.../kafka/clients/consumer/ConsumerRecords.html | 312 +
.../consumer/CooperativeStickyAssignor.html | 324 +
.../kafka/clients/consumer/GroupProtocol.html | 267 +
.../clients/consumer/InvalidOffsetException.html | 189 +
.../kafka/clients/consumer/KafkaConsumer.html | 2719 +++
.../kafka/clients/consumer/KafkaShareConsumer.html | 1046 +
.../clients/consumer/LogTruncationException.html | 217 +
.../kafka/clients/consumer/MockConsumer.html | 1377 ++
.../kafka/clients/consumer/MockShareConsumer.html | 503 +
.../consumer/NoOffsetForPartitionException.html | 202 +
.../kafka/clients/consumer/OffsetAndMetadata.html | 287 +
.../kafka/clients/consumer/OffsetAndTimestamp.html | 238 +
.../clients/consumer/OffsetCommitCallback.html | 157 +
.../consumer/OffsetOutOfRangeException.html | 215 +
.../clients/consumer/OffsetResetStrategy.html | 258 +
.../kafka/clients/consumer/RangeAssignor.html | 318 +
.../consumer/RetriableCommitFailedException.html | 175 +
.../kafka/clients/consumer/RoundRobinAssignor.html | 310 +
.../kafka/clients/consumer/ShareConsumer.html | 430 +
.../kafka/clients/consumer/StickyAssignor.html | 420 +
.../clients/consumer/SubscriptionPattern.html | 204 +
.../kafka/clients/consumer/package-summary.html | 236 +
.../kafka/clients/consumer/package-tree.html | 181 +
.../clients/producer/BufferExhaustedException.html | 164 +
.../apache/kafka/clients/producer/Callback.html | 170 +
.../kafka/clients/producer/KafkaProducer.html | 1050 +
.../kafka/clients/producer/MockProducer.html | 822 +
.../apache/kafka/clients/producer/Partitioner.html | 180 +
.../kafka/clients/producer/PreparedTxnState.html | 253 +
.../apache/kafka/clients/producer/Producer.html | 354 +
.../kafka/clients/producer/ProducerConfig.html | 1232 +
.../clients/producer/ProducerInterceptor.html | 269 +
.../kafka/clients/producer/ProducerRecord.html | 429 +
.../kafka/clients/producer/RecordMetadata.html | 330 +
.../clients/producer/RoundRobinPartitioner.html | 230 +
.../kafka/clients/producer/package-summary.html | 144 +
.../kafka/clients/producer/package-tree.html | 133 +
.../org/apache/kafka/common/ClassicGroupState.html | 275 +
41/javadoc/org/apache/kafka/common/Cluster.html | 588 +
.../org/apache/kafka/common/ClusterResource.html | 210 +
.../kafka/common/ClusterResourceListener.html | 157 +
.../org/apache/kafka/common/Configurable.html | 136 +
.../apache/kafka/common/ConsumerGroupState.html | 328 +
.../org/apache/kafka/common/ElectionType.html | 271 +
41/javadoc/org/apache/kafka/common/Endpoint.html | 263 +
41/javadoc/org/apache/kafka/common/GroupState.html | 327 +
41/javadoc/org/apache/kafka/common/GroupType.html | 266 +
.../kafka/common/InvalidRecordException.html | 167 +
.../org/apache/kafka/common/IsolationLevel.html | 248 +
.../org/apache/kafka/common/KafkaException.html | 179 +
.../kafka/common/KafkaFuture.BaseFunction.html | 134 +
.../kafka/common/KafkaFuture.BiConsumer.html | 136 +
.../org/apache/kafka/common/KafkaFuture.html | 422 +
.../org/apache/kafka/common/MessageFormatter.html | 181 +
41/javadoc/org/apache/kafka/common/Metric.html | 144 +
41/javadoc/org/apache/kafka/common/MetricName.html | 279 +
.../apache/kafka/common/MetricNameTemplate.html | 298 +
41/javadoc/org/apache/kafka/common/Node.html | 335 +
.../org/apache/kafka/common/PartitionInfo.html | 289 +
.../org/apache/kafka/common/Reconfigurable.html | 182 +
.../common/TopicCollection.TopicIdCollection.html | 155 +
.../TopicCollection.TopicNameCollection.html | 155 +
.../org/apache/kafka/common/TopicCollection.html | 175 +
.../org/apache/kafka/common/TopicIdPartition.html | 273 +
.../org/apache/kafka/common/TopicPartition.html | 222 +
.../apache/kafka/common/TopicPartitionInfo.html | 301 +
.../apache/kafka/common/TopicPartitionReplica.html | 233 +
41/javadoc/org/apache/kafka/common/Uuid.html | 380 +
.../kafka/common/acl/AccessControlEntry.html | 277 +
.../kafka/common/acl/AccessControlEntryFilter.html | 337 +
.../org/apache/kafka/common/acl/AclBinding.html | 250 +
.../apache/kafka/common/acl/AclBindingFilter.html | 307 +
.../org/apache/kafka/common/acl/AclOperation.html | 451 +
.../apache/kafka/common/acl/AclPermissionType.html | 302 +
.../apache/kafka/common/acl/package-summary.html | 126 +
.../org/apache/kafka/common/acl/package-tree.html | 89 +
.../annotation/InterfaceStability.Evolving.html | 84 +
.../annotation/InterfaceStability.Stable.html | 89 +
.../annotation/InterfaceStability.Unstable.html | 84 +
.../common/annotation/InterfaceStability.html | 157 +
.../kafka/common/annotation/package-summary.html | 119 +
.../kafka/common/annotation/package-tree.html | 79 +
.../apache/kafka/common/config/AbstractConfig.html | 718 +
.../org/apache/kafka/common/config/Config.html | 158 +
.../kafka/common/config/ConfigChangeCallback.html | 135 +
.../org/apache/kafka/common/config/ConfigData.html | 207 +
.../ConfigDef.CaseInsensitiveValidString.html | 175 +
.../config/ConfigDef.CompositeValidator.html | 175 +
.../kafka/common/config/ConfigDef.ConfigKey.html | 341 +
.../kafka/common/config/ConfigDef.Importance.html | 230 +
.../common/config/ConfigDef.LambdaValidator.html | 177 +
.../kafka/common/config/ConfigDef.ListSize.html | 175 +
.../common/config/ConfigDef.NonEmptyString.html | 193 +
...onfigDef.NonEmptyStringWithoutControlChars.html | 202 +
.../common/config/ConfigDef.NonNullValidator.html | 193 +
.../kafka/common/config/ConfigDef.Range.html | 197 +
.../kafka/common/config/ConfigDef.Recommender.html | 166 +
.../apache/kafka/common/config/ConfigDef.Type.html | 334 +
.../kafka/common/config/ConfigDef.ValidList.html | 175 +
.../kafka/common/config/ConfigDef.ValidString.html | 175 +
.../kafka/common/config/ConfigDef.Validator.html | 145 +
.../kafka/common/config/ConfigDef.Width.html | 238 +
.../org/apache/kafka/common/config/ConfigDef.html | 1422 ++
.../kafka/common/config/ConfigException.html | 173 +
.../kafka/common/config/ConfigResource.Type.html | 272 +
.../apache/kafka/common/config/ConfigResource.html | 253 +
.../kafka/common/config/ConfigTransformer.html | 227 +
.../common/config/ConfigTransformerResult.html | 197 +
.../apache/kafka/common/config/ConfigValue.html | 283 +
.../apache/kafka/common/config/LogLevelConfig.html | 287 +
.../apache/kafka/common/config/SaslConfigs.html | 2136 ++
.../apache/kafka/common/config/SecurityConfig.html | 182 +
.../apache/kafka/common/config/SslClientAuth.html | 277 +
.../org/apache/kafka/common/config/SslConfigs.html | 945 +
.../apache/kafka/common/config/TopicConfig.html | 1293 +
.../kafka/common/config/package-summary.html | 212 +
.../apache/kafka/common/config/package-tree.html | 137 +
.../common/config/provider/ConfigProvider.html | 238 +
.../config/provider/DirectoryConfigProvider.html | 295 +
.../config/provider/EnvVarConfigProvider.html | 303 +
.../common/config/provider/FileConfigProvider.html | 288 +
.../common/config/provider/package-summary.html | 118 +
.../kafka/common/config/provider/package-tree.html | 92 +
.../apache/kafka/common/errors/ApiException.html | 217 +
.../errors/ApplicationRecoverableException.html | 188 +
.../common/errors/AuthenticationException.html | 191 +
.../common/errors/AuthorizationException.html | 171 +
.../common/errors/AuthorizerNotReadyException.html | 158 +
.../errors/BrokerIdNotRegisteredException.html | 165 +
.../common/errors/BrokerNotAvailableException.html | 165 +
.../errors/ClusterAuthorizationException.html | 169 +
.../errors/ConcurrentTransactionsException.html | 157 +
.../common/errors/ControllerMovedException.html | 165 +
.../errors/CoordinatorLoadInProgressException.html | 173 +
.../errors/CoordinatorNotAvailableException.html | 203 +
.../common/errors/CorruptRecordException.html | 185 +
.../DelegationTokenAuthorizationException.html | 169 +
.../errors/DelegationTokenDisabledException.html | 165 +
.../errors/DelegationTokenExpiredException.html | 165 +
.../errors/DelegationTokenNotFoundException.html | 165 +
.../DelegationTokenOwnerMismatchException.html | 165 +
.../kafka/common/errors/DisconnectException.html | 213 +
.../DuplicateBrokerRegistrationException.html | 165 +
.../common/errors/DuplicateResourceException.html | 253 +
.../common/errors/DuplicateSequenceException.html | 155 +
.../common/errors/DuplicateVoterException.html | 165 +
.../common/errors/ElectionNotNeededException.html | 171 +
.../EligibleLeadersNotAvailableException.html | 171 +
.../errors/FeatureUpdateFailedException.html | 165 +
.../common/errors/FencedInstanceIdException.html | 167 +
.../common/errors/FencedLeaderEpochException.html | 174 +
.../common/errors/FencedMemberEpochException.html | 155 +
.../common/errors/FencedStateEpochException.html | 156 +
.../errors/FetchSessionIdNotFoundException.html | 165 +
.../errors/FetchSessionTopicIdException.html | 157 +
.../common/errors/GroupAuthorizationException.html | 217 +
.../common/errors/GroupIdNotFoundException.html | 155 +
.../errors/GroupMaxSizeReachedException.html | 156 +
.../common/errors/GroupNotEmptyException.html | 155 +
.../errors/GroupSubscribedToTopicException.html | 155 +
.../common/errors/IllegalGenerationException.html | 183 +
.../common/errors/IllegalSaslStateException.html | 172 +
.../errors/InconsistentClusterIdException.html | 165 +
.../errors/InconsistentGroupProtocolException.html | 165 +
.../errors/InconsistentTopicIdException.html | 161 +
.../errors/InconsistentVoterSetException.html | 165 +
.../common/errors/IneligibleReplicaException.html | 155 +
.../kafka/common/errors/InterruptException.html | 169 +
.../errors/InvalidCommitOffsetSizeException.html | 165 +
.../errors/InvalidConfigurationException.html | 185 +
.../errors/InvalidFetchSessionEpochException.html | 165 +
.../common/errors/InvalidFetchSizeException.html | 165 +
.../common/errors/InvalidGroupIdException.html | 165 +
.../common/errors/InvalidMetadataException.html | 133 +
.../common/errors/InvalidOffsetException.html | 172 +
.../common/errors/InvalidPartitionsException.html | 165 +
.../common/errors/InvalidPidMappingException.html | 157 +
.../errors/InvalidPrincipalTypeException.html | 165 +
.../errors/InvalidProducerEpochException.html | 161 +
.../common/errors/InvalidRecordStateException.html | 157 +
.../errors/InvalidRegistrationException.html | 156 +
.../common/errors/InvalidRegularExpression.html | 156 +
.../errors/InvalidReplicaAssignmentException.html | 165 +
.../errors/InvalidReplicationFactorException.html | 167 +
.../common/errors/InvalidRequestException.html | 168 +
.../errors/InvalidRequiredAcksException.html | 157 +
.../errors/InvalidSessionTimeoutException.html | 165 +
.../errors/InvalidShareSessionEpochException.html | 158 +
.../common/errors/InvalidTimestampException.html | 166 +
.../kafka/common/errors/InvalidTopicException.html | 236 +
.../common/errors/InvalidTxnStateException.html | 155 +
.../common/errors/InvalidTxnTimeoutException.html | 167 +
.../errors/InvalidUpdateVersionException.html | 165 +
.../common/errors/InvalidVoterKeyException.html | 165 +
.../kafka/common/errors/KafkaStorageException.html | 196 +
.../common/errors/LeaderNotAvailableException.html | 173 +
.../common/errors/ListenerNotFoundException.html | 176 +
.../common/errors/LogDirNotFoundException.html | 174 +
.../common/errors/MemberIdRequiredException.html | 165 +
.../errors/MismatchedEndpointTypeException.html | 155 +
.../kafka/common/errors/NetworkException.html | 189 +
.../common/errors/NewLeaderElectedException.html | 155 +
.../errors/NoReassignmentInProgressException.html | 166 +
.../common/errors/NotControllerException.html | 167 +
.../common/errors/NotCoordinatorException.html | 174 +
.../NotEnoughReplicasAfterAppendException.html | 159 +
.../common/errors/NotEnoughReplicasException.html | 184 +
.../errors/NotLeaderOrFollowerException.html | 193 +
.../common/errors/OffsetMetadataTooLarge.html | 182 +
.../OffsetMovedToTieredStorageException.html | 165 +
.../common/errors/OffsetNotAvailableException.html | 159 +
.../common/errors/OffsetOutOfRangeException.html | 169 +
.../errors/OperationNotAttemptedException.html | 157 +
.../common/errors/OutOfOrderSequenceException.html | 165 +
.../common/errors/PolicyViolationException.html | 166 +
.../common/errors/PositionOutOfRangeException.html | 165 +
.../PreferredLeaderNotAvailableException.html | 171 +
.../errors/PrincipalDeserializationException.html | 166 +
.../common/errors/ProducerFencedException.html | 161 +
.../errors/ReassignmentInProgressException.html | 166 +
.../errors/RebalanceInProgressException.html | 181 +
.../errors/RebootstrapRequiredException.html | 165 +
.../errors/RecordBatchTooLargeException.html | 184 +
...onException.DeserializationExceptionOrigin.html | 221 +
.../errors/RecordDeserializationException.html | 303 +
.../common/errors/RecordTooLargeException.html | 223 +
.../common/errors/RefreshRetriableException.html | 190 +
.../errors/ReplicaNotAvailableException.html | 183 +
.../common/errors/ResourceNotFoundException.html | 252 +
.../kafka/common/errors/RetriableException.html | 186 +
.../common/errors/SaslAuthenticationException.html | 182 +
.../common/errors/SecurityDisabledException.html | 166 +
.../common/errors/SerializationException.html | 181 +
.../errors/ShareSessionLimitReachedException.html | 158 +
.../errors/ShareSessionNotFoundException.html | 158 +
.../common/errors/SnapshotNotFoundException.html | 165 +
.../common/errors/SslAuthenticationException.html | 178 +
.../common/errors/StaleBrokerEpochException.html | 165 +
.../common/errors/StaleMemberEpochException.html | 159 +
.../StreamsInvalidTopologyEpochException.html | 155 +
.../errors/StreamsInvalidTopologyException.html | 155 +
.../errors/StreamsTopologyFencedException.html | 155 +
.../common/errors/TelemetryTooLargeException.html | 156 +
.../errors/ThrottlingQuotaExceededException.html | 199 +
.../kafka/common/errors/TimeoutException.html | 188 +
.../common/errors/TopicAuthorizationException.html | 216 +
.../errors/TopicDeletionDisabledException.html | 163 +
.../kafka/common/errors/TopicExistsException.html | 165 +
.../errors/TransactionAbortableException.html | 165 +
.../common/errors/TransactionAbortedException.html | 175 +
.../TransactionCoordinatorFencedException.html | 165 +
.../TransactionalIdAuthorizationException.html | 159 +
.../errors/TransactionalIdNotFoundException.html | 155 +
.../errors/UnacceptableCredentialException.html | 179 +
.../errors/UnknownControllerIdException.html | 155 +
.../common/errors/UnknownLeaderEpochException.html | 170 +
.../common/errors/UnknownMemberIdException.html | 183 +
.../common/errors/UnknownProducerIdException.html | 161 +
.../common/errors/UnknownServerException.html | 183 +
.../errors/UnknownSubscriptionIdException.html | 156 +
.../common/errors/UnknownTopicIdException.html | 161 +
.../errors/UnknownTopicOrPartitionException.html | 191 +
.../errors/UnreleasedInstanceIdException.html | 155 +
.../errors/UnstableOffsetCommitException.html | 158 +
.../errors/UnsupportedAssignorException.html | 155 +
.../UnsupportedByAuthenticationException.html | 166 +
.../UnsupportedCompressionTypeException.html | 166 +
.../errors/UnsupportedEndpointTypeException.html | 155 +
.../UnsupportedForMessageFormatException.html | 169 +
.../errors/UnsupportedSaslMechanismException.html | 171 +
.../common/errors/UnsupportedVersionException.html | 175 +
.../common/errors/VoterNotFoundException.html | 165 +
.../kafka/common/errors/WakeupException.html | 154 +
.../kafka/common/errors/package-summary.html | 579 +
.../apache/kafka/common/errors/package-tree.html | 282 +
.../org/apache/kafka/common/header/Header.html | 133 +
.../org/apache/kafka/common/header/Headers.html | 241 +
.../kafka/common/header/package-summary.html | 100 +
.../apache/kafka/common/header/package-tree.html | 72 +
.../metrics/CompoundStat.NamedMeasurable.html | 173 +
.../apache/kafka/common/metrics/CompoundStat.html | 153 +
.../org/apache/kafka/common/metrics/Gauge.html | 145 +
.../apache/kafka/common/metrics/JmxReporter.html | 468 +
.../apache/kafka/common/metrics/KafkaMetric.html | 279 +
.../kafka/common/metrics/KafkaMetricsContext.html | 209 +
.../apache/kafka/common/metrics/Measurable.html | 150 +
.../kafka/common/metrics/MeasurableStat.html | 107 +
.../apache/kafka/common/metrics/MetricConfig.html | 297 +
.../kafka/common/metrics/MetricValueProvider.html | 94 +
.../org/apache/kafka/common/metrics/Metrics.html | 946 +
.../kafka/common/metrics/MetricsContext.html | 192 +
.../kafka/common/metrics/MetricsReporter.html | 273 +
.../apache/kafka/common/metrics/Monitorable.html | 131 +
.../apache/kafka/common/metrics/PluginMetrics.html | 221 +
.../org/apache/kafka/common/metrics/Quota.html | 236 +
.../common/metrics/QuotaViolationException.html | 230 +
.../common/metrics/Sensor.RecordingLevel.html | 312 +
.../org/apache/kafka/common/metrics/Sensor.html | 380 +
.../org/apache/kafka/common/metrics/Stat.html | 146 +
.../kafka/common/metrics/package-summary.html | 182 +
.../apache/kafka/common/metrics/package-tree.html | 147 +
.../org/apache/kafka/common/metrics/stats/Avg.html | 176 +
.../common/metrics/stats/CumulativeCount.html | 191 +
.../kafka/common/metrics/stats/CumulativeSum.html | 232 +
.../kafka/common/metrics/stats/Frequencies.html | 287 +
.../kafka/common/metrics/stats/Frequency.html | 205 +
.../common/metrics/stats/Histogram.BinScheme.html | 179 +
.../metrics/stats/Histogram.ConstantBinScheme.html | 236 +
.../metrics/stats/Histogram.LinearBinScheme.html | 234 +
.../kafka/common/metrics/stats/Histogram.html | 228 +
.../org/apache/kafka/common/metrics/stats/Max.html | 176 +
.../apache/kafka/common/metrics/stats/Meter.html | 267 +
.../org/apache/kafka/common/metrics/stats/Min.html | 176 +
.../kafka/common/metrics/stats/Percentile.html | 169 +
.../metrics/stats/Percentiles.BucketSizing.html | 221 +
.../kafka/common/metrics/stats/Percentiles.html | 246 +
.../apache/kafka/common/metrics/stats/Rate.html | 270 +
.../kafka/common/metrics/stats/SampledStat.html | 259 +
.../kafka/common/metrics/stats/SimpleRate.html | 181 +
.../kafka/common/metrics/stats/TokenBucket.html | 254 +
.../apache/kafka/common/metrics/stats/Value.html | 204 +
.../kafka/common/metrics/stats/WindowedCount.html | 148 +
.../kafka/common/metrics/stats/WindowedSum.html | 183 +
.../common/metrics/stats/package-summary.html | 191 +
.../kafka/common/metrics/stats/package-tree.html | 122 +
.../org/apache/kafka/common/package-summary.html | 253 +
.../org/apache/kafka/common/package-tree.html | 157 +
.../common/quota/ClientQuotaAlteration.Op.html | 227 +
.../kafka/common/quota/ClientQuotaAlteration.html | 211 +
.../kafka/common/quota/ClientQuotaEntity.html | 293 +
.../kafka/common/quota/ClientQuotaFilter.html | 234 +
.../common/quota/ClientQuotaFilterComponent.html | 248 +
.../apache/kafka/common/quota/package-summary.html | 114 +
.../apache/kafka/common/quota/package-tree.html | 75 +
.../apache/kafka/common/resource/PatternType.html | 334 +
.../org/apache/kafka/common/resource/Resource.html | 287 +
.../kafka/common/resource/ResourcePattern.html | 308 +
.../common/resource/ResourcePatternFilter.html | 334 +
.../apache/kafka/common/resource/ResourceType.html | 349 +
.../kafka/common/resource/package-summary.html | 123 +
.../apache/kafka/common/resource/package-tree.html | 88 +
.../security/auth/AuthenticateCallbackHandler.html | 179 +
.../security/auth/AuthenticationContext.html | 158 +
.../kafka/common/security/auth/KafkaPrincipal.html | 320 +
.../security/auth/KafkaPrincipalBuilder.html | 145 +
.../common/security/auth/KafkaPrincipalSerde.html | 159 +
.../apache/kafka/common/security/auth/Login.html | 202 +
.../auth/PlaintextAuthenticationContext.html | 207 +
.../security/auth/SaslAuthenticationContext.html | 250 +
.../kafka/common/security/auth/SaslExtensions.html | 267 +
.../security/auth/SaslExtensionsCallback.html | 190 +
.../common/security/auth/SecurityProtocol.html | 319 +
.../security/auth/SecurityProviderCreator.html | 151 +
.../security/auth/SslAuthenticationContext.html | 218 +
.../common/security/auth/SslEngineFactory.html | 251 +
.../common/security/auth/package-summary.html | 137 +
.../kafka/common/security/auth/package-tree.html | 119 +
.../BrokerJwtValidator.ClaimSupplier.html | 133 +
.../security/oauthbearer/BrokerJwtValidator.html | 241 +
.../oauthbearer/ClientCredentialsJwtRetriever.html | 276 +
.../security/oauthbearer/ClientJwtValidator.html | 268 +
.../security/oauthbearer/DefaultJwtRetriever.html | 235 +
.../security/oauthbearer/DefaultJwtValidator.html | 229 +
.../security/oauthbearer/FileJwtRetriever.html | 205 +
.../oauthbearer/JwtBearerJwtRetriever.html | 295 +
.../common/security/oauthbearer/JwtRetriever.html | 170 +
.../oauthbearer/JwtRetrieverException.html | 170 +
.../common/security/oauthbearer/JwtValidator.html | 179 +
.../oauthbearer/JwtValidatorException.html | 173 +
.../OAuthBearerExtensionsValidatorCallback.html | 271 +
.../OAuthBearerLoginCallbackHandler.html | 454 +
.../oauthbearer/OAuthBearerLoginModule.html | 468 +
.../security/oauthbearer/OAuthBearerToken.html | 246 +
.../oauthbearer/OAuthBearerTokenCallback.html | 279 +
.../oauthbearer/OAuthBearerValidatorCallback.html | 311 +
.../OAuthBearerValidatorCallbackHandler.html | 288 +
.../security/oauthbearer/package-summary.html | 200 +
.../common/security/oauthbearer/package-tree.html | 122 +
.../security/plain/PlainAuthenticateCallback.html | 203 +
.../common/security/plain/PlainLoginModule.html | 225 +
.../common/security/plain/package-summary.html | 87 +
.../kafka/common/security/plain/package-tree.html | 72 +
.../common/security/scram/ScramCredential.html | 209 +
.../security/scram/ScramCredentialCallback.html | 179 +
.../security/scram/ScramExtensionsCallback.html | 183 +
.../common/security/scram/ScramLoginModule.html | 262 +
.../common/security/scram/package-summary.html | 99 +
.../kafka/common/security/scram/package-tree.html | 74 +
.../security/token/delegation/DelegationToken.html | 218 +
.../token/delegation/TokenInformation.html | 348 +
.../security/token/delegation/package-summary.html | 91 +
.../security/token/delegation/package-tree.html | 72 +
.../common/serialization/BooleanDeserializer.html | 223 +
.../common/serialization/BooleanSerializer.html | 183 +
.../serialization/ByteArrayDeserializer.html | 183 +
.../common/serialization/ByteArraySerializer.html | 183 +
.../serialization/ByteBufferDeserializer.html | 223 +
.../common/serialization/ByteBufferSerializer.html | 190 +
.../common/serialization/BytesDeserializer.html | 183 +
.../common/serialization/BytesSerializer.html | 183 +
.../kafka/common/serialization/Deserializer.html | 265 +
.../common/serialization/DoubleDeserializer.html | 223 +
.../common/serialization/DoubleSerializer.html | 183 +
.../common/serialization/FloatDeserializer.html | 223 +
.../common/serialization/FloatSerializer.html | 183 +
.../common/serialization/IntegerDeserializer.html | 223 +
.../common/serialization/IntegerSerializer.html | 183 +
.../common/serialization/ListDeserializer.html | 247 +
.../kafka/common/serialization/ListSerializer.html | 245 +
.../common/serialization/LongDeserializer.html | 223 +
.../kafka/common/serialization/LongSerializer.html | 183 +
.../apache/kafka/common/serialization/Serde.html | 188 +
.../common/serialization/Serdes.BooleanSerde.html | 140 +
.../serialization/Serdes.ByteArraySerde.html | 140 +
.../serialization/Serdes.ByteBufferSerde.html | 140 +
.../common/serialization/Serdes.BytesSerde.html | 140 +
.../common/serialization/Serdes.DoubleSerde.html | 140 +
.../common/serialization/Serdes.FloatSerde.html | 140 +
.../common/serialization/Serdes.IntegerSerde.html | 140 +
.../common/serialization/Serdes.ListSerde.html | 150 +
.../common/serialization/Serdes.LongSerde.html | 140 +
.../common/serialization/Serdes.ShortSerde.html | 140 +
.../common/serialization/Serdes.StringSerde.html | 140 +
.../common/serialization/Serdes.UUIDSerde.html | 140 +
.../common/serialization/Serdes.VoidSerde.html | 140 +
.../common/serialization/Serdes.WrapperSerde.html | 235 +
.../apache/kafka/common/serialization/Serdes.html | 390 +
.../kafka/common/serialization/Serializer.html | 228 +
.../common/serialization/ShortDeserializer.html | 223 +
.../common/serialization/ShortSerializer.html | 183 +
.../common/serialization/StringDeserializer.html | 247 +
.../common/serialization/StringSerializer.html | 207 +
.../common/serialization/UUIDDeserializer.html | 247 +
.../kafka/common/serialization/UUIDSerializer.html | 207 +
.../common/serialization/VoidDeserializer.html | 223 +
.../kafka/common/serialization/VoidSerializer.html | 183 +
.../common/serialization/package-summary.html | 211 +
.../kafka/common/serialization/package-tree.html | 130 +
.../apache/kafka/connect/components/Versioned.html | 140 +
.../kafka/connect/components/package-summary.html | 87 +
.../kafka/connect/components/package-tree.html | 67 +
.../kafka/connect/connector/ConnectRecord.html | 388 +
.../apache/kafka/connect/connector/Connector.html | 341 +
.../kafka/connect/connector/ConnectorContext.html | 183 +
.../org/apache/kafka/connect/connector/Task.html | 174 +
.../kafka/connect/connector/package-summary.html | 122 +
.../kafka/connect/connector/package-tree.html | 79 +
.../ConnectorClientConfigOverridePolicy.html | 163 +
.../ConnectorClientConfigRequest.ClientType.html | 229 +
.../policy/ConnectorClientConfigRequest.html | 269 +
.../connect/connector/policy/package-summary.html | 113 +
.../connect/connector/policy/package-tree.html | 100 +
.../apache/kafka/connect/data/ConnectSchema.html | 545 +
41/javadoc/org/apache/kafka/connect/data/Date.html | 258 +
.../org/apache/kafka/connect/data/Decimal.html | 285 +
.../org/apache/kafka/connect/data/Field.html | 243 +
.../org/apache/kafka/connect/data/Schema.Type.html | 368 +
.../org/apache/kafka/connect/data/Schema.html | 515 +
.../apache/kafka/connect/data/SchemaAndValue.html | 238 +
.../apache/kafka/connect/data/SchemaBuilder.html | 772 +
.../apache/kafka/connect/data/SchemaProjector.html | 180 +
.../org/apache/kafka/connect/data/Struct.html | 488 +
41/javadoc/org/apache/kafka/connect/data/Time.html | 258 +
.../org/apache/kafka/connect/data/Timestamp.html | 256 +
.../org/apache/kafka/connect/data/Values.html | 589 +
.../apache/kafka/connect/data/package-summary.html | 149 +
.../apache/kafka/connect/data/package-tree.html | 101 +
.../connect/errors/AlreadyExistsException.html | 171 +
.../kafka/connect/errors/ConnectException.html | 173 +
.../apache/kafka/connect/errors/DataException.html | 175 +
.../errors/IllegalWorkerStateException.html | 171 +
.../kafka/connect/errors/NotFoundException.html | 171 +
.../kafka/connect/errors/RetriableException.html | 171 +
.../connect/errors/SchemaBuilderException.html | 173 +
.../connect/errors/SchemaProjectorException.html | 173 +
.../kafka/connect/errors/package-summary.html | 115 +
.../apache/kafka/connect/errors/package-tree.html | 100 +
.../kafka/connect/header/ConnectHeaders.html | 913 +
.../org/apache/kafka/connect/header/Header.html | 206 +
.../connect/header/Headers.HeaderTransform.html | 139 +
.../org/apache/kafka/connect/header/Headers.html | 751 +
.../kafka/connect/header/package-summary.html | 105 +
.../apache/kafka/connect/header/package-tree.html | 83 +
.../apache/kafka/connect/health/AbstractState.html | 241 +
.../connect/health/ConnectClusterDetails.html | 133 +
.../kafka/connect/health/ConnectClusterState.html | 197 +
.../kafka/connect/health/ConnectorHealth.html | 259 +
.../kafka/connect/health/ConnectorState.html | 181 +
.../apache/kafka/connect/health/ConnectorType.html | 248 +
.../org/apache/kafka/connect/health/TaskState.html | 226 +
.../kafka/connect/health/package-summary.html | 119 +
.../apache/kafka/connect/health/package-tree.html | 98 +
.../apache/kafka/connect/mirror/Checkpoint.html | 443 +
.../connect/mirror/DefaultReplicationPolicy.html | 389 +
.../org/apache/kafka/connect/mirror/Heartbeat.html | 335 +
.../connect/mirror/IdentityReplicationPolicy.html | 292 +
.../apache/kafka/connect/mirror/MirrorClient.html | 320 +
.../kafka/connect/mirror/MirrorClientConfig.html | 404 +
.../kafka/connect/mirror/RemoteClusterUtils.html | 251 +
.../kafka/connect/mirror/ReplicationPolicy.html | 261 +
.../kafka/connect/mirror/SourceAndTarget.html | 209 +
.../kafka/connect/mirror/package-summary.html | 126 +
.../apache/kafka/connect/mirror/package-tree.html | 91 +
.../kafka/connect/rest/ConnectRestExtension.html | 169 +
.../connect/rest/ConnectRestExtensionContext.html | 150 +
.../apache/kafka/connect/rest/package-summary.html | 92 +
.../apache/kafka/connect/rest/package-tree.html | 86 +
.../kafka/connect/sink/ErrantRecordReporter.html | 160 +
.../apache/kafka/connect/sink/SinkConnector.html | 266 +
.../kafka/connect/sink/SinkConnectorContext.html | 98 +
.../org/apache/kafka/connect/sink/SinkRecord.html | 520 +
.../org/apache/kafka/connect/sink/SinkTask.html | 432 +
.../apache/kafka/connect/sink/SinkTaskContext.html | 328 +
.../apache/kafka/connect/sink/package-summary.html | 116 +
.../apache/kafka/connect/sink/package-tree.html | 93 +
.../source/ConnectorTransactionBoundaries.html | 224 +
.../kafka/connect/source/ExactlyOnceSupport.html | 224 +
.../kafka/connect/source/SourceConnector.html | 286 +
.../connect/source/SourceConnectorContext.html | 140 +
.../apache/kafka/connect/source/SourceRecord.html | 428 +
.../source/SourceTask.TransactionBoundary.html | 306 +
.../apache/kafka/connect/source/SourceTask.html | 356 +
.../kafka/connect/source/SourceTaskContext.html | 211 +
.../kafka/connect/source/TransactionContext.html | 194 +
.../kafka/connect/source/package-summary.html | 130 +
.../apache/kafka/connect/source/package-tree.html | 109 +
.../apache/kafka/connect/storage/Converter.html | 296 +
.../kafka/connect/storage/ConverterConfig.html | 204 +
.../kafka/connect/storage/ConverterType.html | 253 +
.../kafka/connect/storage/HeaderConverter.html | 207 +
.../kafka/connect/storage/OffsetStorageReader.html | 173 +
.../connect/storage/SimpleHeaderConverter.html | 286 +
.../kafka/connect/storage/StringConverter.html | 371 +
.../connect/storage/StringConverterConfig.html | 237 +
.../kafka/connect/storage/package-summary.html | 125 +
.../apache/kafka/connect/storage/package-tree.html | 116 +
.../apache/kafka/connect/tools/MockConnector.html | 392 +
.../kafka/connect/tools/MockSinkConnector.html | 382 +
.../apache/kafka/connect/tools/MockSinkTask.html | 255 +
.../kafka/connect/tools/MockSourceConnector.html | 373 +
.../apache/kafka/connect/tools/MockSourceTask.html | 266 +
.../kafka/connect/tools/SchemaSourceConnector.html | 278 +
.../kafka/connect/tools/SchemaSourceTask.html | 399 +
.../connect/tools/VerifiableSinkConnector.html | 294 +
.../kafka/connect/tools/VerifiableSinkTask.html | 331 +
.../connect/tools/VerifiableSourceConnector.html | 285 +
.../kafka/connect/tools/VerifiableSourceTask.html | 404 +
.../kafka/connect/tools/package-summary.html | 128 +
.../apache/kafka/connect/tools/package-tree.html | 101 +
.../kafka/connect/transforms/Transformation.html | 194 +
.../kafka/connect/transforms/package-summary.html | 100 +
.../kafka/connect/transforms/package-tree.html | 80 +
.../connect/transforms/predicates/Predicate.html | 187 +
.../transforms/predicates/package-summary.html | 100 +
.../transforms/predicates/package-tree.html | 76 +
.../apache/kafka/connect/util/ConnectorUtils.html | 177 +
.../apache/kafka/connect/util/package-summary.html | 87 +
.../apache/kafka/connect/util/package-tree.html | 71 +
.../assignor/ConsumerGroupPartitionAssignor.html | 98 +
.../group/api/assignor/GroupAssignment.html | 202 +
.../coordinator/group/api/assignor/GroupSpec.html | 228 +
.../group/api/assignor/MemberAssignment.html | 129 +
.../group/api/assignor/MemberSubscription.html | 164 +
.../group/api/assignor/PartitionAssignor.html | 156 +
.../api/assignor/PartitionAssignorException.html | 167 +
.../api/assignor/ShareGroupPartitionAssignor.html | 99 +
.../api/assignor/SubscribedTopicDescriber.html | 158 +
.../group/api/assignor/SubscriptionType.html | 241 +
.../group/api/assignor/package-summary.html | 130 +
.../group/api/assignor/package-tree.html | 121 +
.../kafka/server/authorizer/AclCreateResult.html | 190 +
.../AclDeleteResult.AclBindingDeleteResult.html | 190 +
.../kafka/server/authorizer/AclDeleteResult.html | 200 +
.../org/apache/kafka/server/authorizer/Action.html | 275 +
.../authorizer/AuthorizableRequestContext.html | 214 +
.../server/authorizer/AuthorizationResult.html | 217 +
.../apache/kafka/server/authorizer/Authorizer.html | 338 +
.../server/authorizer/AuthorizerServerInfo.html | 178 +
.../kafka/server/authorizer/package-summary.html | 114 +
.../kafka/server/authorizer/package-tree.html | 109 +
.../server/log/remote/storage/LogSegmentData.html | 291 +
.../log/remote/storage/RemoteLogMetadata.html | 167 +
.../remote/storage/RemoteLogMetadataManager.html | 482 +
.../log/remote/storage/RemoteLogSegmentId.html | 237 +
.../RemoteLogSegmentMetadata.CustomMetadata.html | 214 +
.../remote/storage/RemoteLogSegmentMetadata.html | 541 +
.../storage/RemoteLogSegmentMetadataUpdate.html | 265 +
.../log/remote/storage/RemoteLogSegmentState.html | 297 +
.../storage/RemotePartitionDeleteMetadata.html | 238 +
.../remote/storage/RemotePartitionDeleteState.html | 286 +
.../storage/RemoteResourceNotFoundException.html | 170 +
.../log/remote/storage/RemoteStorageException.html | 170 +
.../storage/RemoteStorageManager.IndexType.html | 261 +
.../log/remote/storage/RemoteStorageManager.html | 303 +
.../log/remote/storage/RemoteStorageMetrics.html | 387 +
.../server/log/remote/storage/package-summary.html | 153 +
.../server/log/remote/storage/package-tree.html | 131 +
.../policy/AlterConfigPolicy.RequestMetadata.html | 221 +
.../kafka/server/policy/AlterConfigPolicy.html | 176 +
.../policy/CreateTopicPolicy.RequestMetadata.html | 279 +
.../kafka/server/policy/CreateTopicPolicy.html | 175 +
.../kafka/server/policy/package-summary.html | 105 +
.../apache/kafka/server/policy/package-tree.html | 89 +
.../kafka/server/quota/ClientQuotaCallback.html | 288 +
.../quota/ClientQuotaEntity.ConfigEntity.html | 147 +
.../quota/ClientQuotaEntity.ConfigEntityType.html | 238 +
.../kafka/server/quota/ClientQuotaEntity.html | 154 +
.../apache/kafka/server/quota/ClientQuotaType.html | 234 +
.../apache/kafka/server/quota/package-summary.html | 109 +
.../apache/kafka/server/quota/package-tree.html | 88 +
.../kafka/server/telemetry/ClientTelemetry.html | 135 +
.../server/telemetry/ClientTelemetryPayload.html | 181 +
.../server/telemetry/ClientTelemetryReceiver.html | 141 +
.../kafka/server/telemetry/package-summary.html | 97 +
.../kafka/server/telemetry/package-tree.html | 69 +
.../org/apache/kafka/streams/AutoOffsetReset.html | 219 +
.../apache/kafka/streams/ClientInstanceIds.html | 167 +
.../org/apache/kafka/streams/GroupProtocol.html | 267 +
.../apache/kafka/streams/KafkaClientSupplier.html | 218 +
.../kafka/streams/KafkaStreams.CloseOptions.html | 172 +
.../apache/kafka/streams/KafkaStreams.State.html | 367 +
.../kafka/streams/KafkaStreams.StateListener.html | 139 +
.../org/apache/kafka/streams/KafkaStreams.html | 989 +
.../org/apache/kafka/streams/KeyQueryMetadata.html | 278 +
41/javadoc/org/apache/kafka/streams/KeyValue.html | 275 +
41/javadoc/org/apache/kafka/streams/LagInfo.html | 213 +
.../apache/kafka/streams/StoreQueryParameters.html | 273 +
.../org/apache/kafka/streams/StreamsBuilder.html | 790 +
.../streams/StreamsConfig.InternalConfig.html | 400 +
.../org/apache/kafka/streams/StreamsConfig.html | 3162 +++
.../org/apache/kafka/streams/StreamsMetadata.html | 277 +
.../org/apache/kafka/streams/StreamsMetrics.html | 334 +
.../org/apache/kafka/streams/TaskMetadata.html | 238 +
.../org/apache/kafka/streams/TestInputTopic.html | 404 +
.../org/apache/kafka/streams/TestOutputTopic.html | 320 +
.../org/apache/kafka/streams/ThreadMetadata.html | 297 +
.../kafka/streams/Topology.AutoOffsetReset.html | 238 +
41/javadoc/org/apache/kafka/streams/Topology.html | 1314 ++
.../kafka/streams/TopologyConfig.TaskConfig.html | 187 +
.../org/apache/kafka/streams/TopologyConfig.html | 387 +
.../streams/TopologyDescription.GlobalStore.html | 166 +
.../kafka/streams/TopologyDescription.Node.html | 176 +
.../streams/TopologyDescription.Processor.html | 144 +
.../kafka/streams/TopologyDescription.Sink.html | 162 +
.../kafka/streams/TopologyDescription.Source.html | 160 +
.../streams/TopologyDescription.Subtopology.html | 157 +
.../apache/kafka/streams/TopologyDescription.html | 199 +
.../apache/kafka/streams/TopologyTestDriver.html | 794 +
.../streams/errors/BrokerNotFoundException.html | 176 +
.../errors/DefaultProductionExceptionHandler.html | 245 +
...tionHandler.DeserializationHandlerResponse.html | 272 +
.../errors/DeserializationExceptionHandler.html | 204 +
.../kafka/streams/errors/ErrorHandlerContext.html | 347 +
.../streams/errors/InvalidStateStoreException.html | 179 +
.../InvalidStateStorePartitionException.html | 171 +
.../apache/kafka/streams/errors/LockException.html | 175 +
.../errors/LogAndContinueExceptionHandler.html | 246 +
.../LogAndContinueProcessingExceptionHandler.html | 209 +
.../streams/errors/LogAndFailExceptionHandler.html | 246 +
.../LogAndFailProcessingExceptionHandler.html | 209 +
.../errors/MissingSourceTopicException.html | 155 +
...ExceptionHandler.ProcessingHandlerResponse.html | 271 +
.../streams/errors/ProcessingExceptionHandler.html | 167 +
.../streams/errors/ProcessorStateException.html | 175 +
...Handler.ProductionExceptionHandlerResponse.html | 296 +
...eptionHandler.SerializationExceptionOrigin.html | 227 +
.../streams/errors/ProductionExceptionHandler.html | 257 +
.../errors/StateStoreMigratedException.html | 172 +
.../errors/StateStoreNotAvailableException.html | 171 +
.../kafka/streams/errors/StreamsException.html | 254 +
.../streams/errors/StreamsNotStartedException.html | 170 +
.../errors/StreamsRebalancingException.html | 170 +
.../streams/errors/StreamsStoppedException.html | 169 +
...ptionHandler.StreamThreadExceptionResponse.html | 283 +
.../errors/StreamsUncaughtExceptionHandler.html | 150 +
.../streams/errors/TaskAssignmentException.html | 176 +
.../streams/errors/TaskCorruptedException.html | 202 +
.../streams/errors/TaskIdFormatException.html | 176 +
.../streams/errors/TaskMigratedException.html | 168 +
.../kafka/streams/errors/TopologyException.html | 175 +
.../streams/errors/UnknownStateStoreException.html | 169 +
.../streams/errors/UnknownTopologyException.html | 171 +
.../kafka/streams/errors/package-summary.html | 267 +
.../apache/kafka/streams/errors/package-tree.html | 148 +
.../apache/kafka/streams/kstream/Aggregator.html | 171 +
.../org/apache/kafka/streams/kstream/Branched.html | 283 +
.../kafka/streams/kstream/BranchedKStream.html | 319 +
.../kafka/streams/kstream/CogroupedKStream.html | 478 +
.../org/apache/kafka/streams/kstream/Consumed.html | 483 +
.../streams/kstream/EmitStrategy.StrategyType.html | 230 +
.../apache/kafka/streams/kstream/EmitStrategy.html | 236 +
.../kafka/streams/kstream/ForeachAction.html | 158 +
.../kafka/streams/kstream/ForeachProcessor.html | 185 +
.../apache/kafka/streams/kstream/GlobalKTable.html | 185 +
.../org/apache/kafka/streams/kstream/Grouped.html | 351 +
.../apache/kafka/streams/kstream/Initializer.html | 156 +
.../apache/kafka/streams/kstream/JoinWindows.html | 483 +
.../org/apache/kafka/streams/kstream/Joined.html | 524 +
.../kafka/streams/kstream/KGroupedStream.html | 820 +
.../kafka/streams/kstream/KGroupedTable.html | 916 +
.../org/apache/kafka/streams/kstream/KStream.html | 2443 ++
.../org/apache/kafka/streams/kstream/KTable.html | 3522 +++
.../kafka/streams/kstream/KeyValueMapper.html | 174 +
.../streams/kstream/Materialized.StoreType.html | 280 +
.../apache/kafka/streams/kstream/Materialized.html | 549 +
.../org/apache/kafka/streams/kstream/Merger.html | 150 +
.../org/apache/kafka/streams/kstream/Named.html | 151 +
.../apache/kafka/streams/kstream/Predicate.html | 161 +
.../org/apache/kafka/streams/kstream/Printed.html | 248 +
.../org/apache/kafka/streams/kstream/Produced.html | 402 +
.../org/apache/kafka/streams/kstream/Reducer.html | 166 +
.../kafka/streams/kstream/Repartitioned.html | 350 +
.../kstream/SessionWindowedCogroupedKStream.html | 376 +
.../kstream/SessionWindowedDeserializer.html | 276 +
.../streams/kstream/SessionWindowedKStream.html | 906 +
.../streams/kstream/SessionWindowedSerializer.html | 291 +
.../kafka/streams/kstream/SessionWindows.html | 292 +
.../kafka/streams/kstream/SlidingWindows.html | 281 +
.../apache/kafka/streams/kstream/StreamJoined.html | 461 +
.../streams/kstream/Suppressed.BufferConfig.html | 289 +
.../kstream/Suppressed.EagerBufferConfig.html | 104 +
.../kstream/Suppressed.StrictBufferConfig.html | 103 +
.../apache/kafka/streams/kstream/Suppressed.html | 227 +
.../apache/kafka/streams/kstream/TableJoined.html | 265 +
.../kstream/TimeWindowedCogroupedKStream.html | 359 +
.../streams/kstream/TimeWindowedDeserializer.html | 316 +
.../kafka/streams/kstream/TimeWindowedKStream.html | 915 +
.../streams/kstream/TimeWindowedSerializer.html | 291 +
.../apache/kafka/streams/kstream/TimeWindows.html | 392 +
.../apache/kafka/streams/kstream/Transformer.html | 228 +
.../kafka/streams/kstream/TransformerSupplier.html | 178 +
.../kafka/streams/kstream/UnlimitedWindows.html | 310 +
.../apache/kafka/streams/kstream/ValueJoiner.html | 171 +
.../kafka/streams/kstream/ValueJoinerWithKey.html | 178 +
.../apache/kafka/streams/kstream/ValueMapper.html | 164 +
.../kafka/streams/kstream/ValueMapperWithKey.html | 169 +
.../kafka/streams/kstream/ValueTransformer.html | 226 +
.../streams/kstream/ValueTransformerSupplier.html | 176 +
.../streams/kstream/ValueTransformerWithKey.html | 227 +
.../kstream/ValueTransformerWithKeySupplier.html | 172 +
.../org/apache/kafka/streams/kstream/Window.html | 303 +
.../org/apache/kafka/streams/kstream/Windowed.html | 241 +
.../WindowedSerdes.SessionWindowedSerde.html | 148 +
.../kstream/WindowedSerdes.TimeWindowedSerde.html | 181 +
.../kafka/streams/kstream/WindowedSerdes.html | 195 +
.../org/apache/kafka/streams/kstream/Windows.html | 201 +
.../kafka/streams/kstream/package-summary.html | 364 +
.../apache/kafka/streams/kstream/package-tree.html | 174 +
.../org/apache/kafka/streams/package-summary.html | 253 +
.../org/apache/kafka/streams/package-tree.html | 128 +
.../processor/BatchingStateRestoreCallback.html | 155 +
.../kafka/streams/processor/Cancellable.html | 141 +
.../kafka/streams/processor/CommitCallback.html | 136 +
.../streams/processor/ConnectedStoreProvider.html | 206 +
.../streams/processor/FailOnInvalidTimestamp.html | 230 +
.../processor/LogAndSkipOnInvalidTimestamp.html | 231 +
.../MockProcessorContext.CapturedForward.html | 196 +
.../MockProcessorContext.CapturedPunctuator.html | 172 +
.../streams/processor/MockProcessorContext.html | 1094 +
.../kafka/streams/processor/ProcessorContext.html | 602 +
.../kafka/streams/processor/PunctuationType.html | 228 +
.../apache/kafka/streams/processor/Punctuator.html | 158 +
.../kafka/streams/processor/RecordContext.html | 290 +
.../StandbyUpdateListener.SuspendReason.html | 221 +
.../streams/processor/StandbyUpdateListener.html | 227 +
.../streams/processor/StateRestoreCallback.html | 137 +
.../streams/processor/StateRestoreListener.html | 245 +
.../apache/kafka/streams/processor/StateStore.html | 293 +
.../kafka/streams/processor/StateStoreContext.html | 333 +
.../kafka/streams/processor/StreamPartitioner.html | 187 +
.../org/apache/kafka/streams/processor/TaskId.html | 301 +
.../streams/processor/TimestampExtractor.html | 161 +
.../org/apache/kafka/streams/processor/To.html | 218 +
.../streams/processor/TopicNameExtractor.html | 146 +
.../UsePartitionTimeOnInvalidTimestamp.html | 230 +
.../processor/WallclockTimestampExtractor.html | 193 +
.../processor/api/ContextualFixedKeyProcessor.html | 162 +
.../streams/processor/api/ContextualProcessor.html | 163 +
.../streams/processor/api/FixedKeyProcessor.html | 185 +
.../processor/api/FixedKeyProcessorContext.html | 227 +
.../processor/api/FixedKeyProcessorSupplier.html | 165 +
.../streams/processor/api/FixedKeyRecord.html | 289 +
.../api/InternalFixedKeyRecordFactory.html | 147 +
.../api/MockProcessorContext.CapturedForward.html | 235 +
.../MockProcessorContext.CapturedPunctuator.html | 172 +
.../processor/api/MockProcessorContext.html | 862 +
.../streams/processor/api/ProcessingContext.html | 434 +
.../kafka/streams/processor/api/Processor.html | 186 +
.../streams/processor/api/ProcessorContext.html | 231 +
.../streams/processor/api/ProcessorSupplier.html | 170 +
.../streams/processor/api/ProcessorWrapper.html | 234 +
.../apache/kafka/streams/processor/api/Record.html | 390 +
.../streams/processor/api/RecordMetadata.html | 190 +
.../api/WrappedFixedKeyProcessorSupplier.html | 110 +
.../processor/api/WrappedProcessorSupplier.html | 110 +
.../streams/processor/api/package-summary.html | 182 +
.../kafka/streams/processor/api/package-tree.html | 125 +
.../processor/assignment/ApplicationState.html | 166 +
.../processor/assignment/AssignmentConfigs.html | 336 +
.../KafkaStreamsAssignment.AssignedTask.Type.html | 221 +
.../KafkaStreamsAssignment.AssignedTask.html | 235 +
.../assignment/KafkaStreamsAssignment.html | 259 +
.../processor/assignment/KafkaStreamsState.html | 293 +
.../streams/processor/assignment/ProcessId.html | 233 +
...skAssignmentUtils.MoveStandbyTaskPredicate.html | 139 +
...ssignmentUtils.RackAwareOptimizationParams.html | 200 +
.../processor/assignment/TaskAssignmentUtils.html | 293 +
.../assignment/TaskAssignor.AssignmentError.html | 259 +
.../assignment/TaskAssignor.TaskAssignment.html | 168 +
.../streams/processor/assignment/TaskAssignor.html | 225 +
.../streams/processor/assignment/TaskInfo.html | 173 +
.../processor/assignment/TaskTopicPartition.html | 174 +
.../assignment/assignors/StickyTaskAssignor.html | 245 +
.../assignment/assignors/package-summary.html | 98 +
.../assignment/assignors/package-tree.html | 71 +
.../processor/assignment/package-summary.html | 174 +
.../streams/processor/assignment/package-tree.html | 107 +
.../kafka/streams/processor/package-summary.html | 240 +
.../kafka/streams/processor/package-tree.html | 117 +
.../apache/kafka/streams/query/FailureReason.html | 286 +
.../org/apache/kafka/streams/query/KeyQuery.html | 198 +
.../streams/query/MultiVersionedKeyQuery.html | 293 +
.../org/apache/kafka/streams/query/Position.html | 280 +
.../apache/kafka/streams/query/PositionBound.html | 213 +
.../org/apache/kafka/streams/query/Query.html | 96 +
.../apache/kafka/streams/query/QueryConfig.html | 160 +
.../apache/kafka/streams/query/QueryResult.html | 316 +
.../org/apache/kafka/streams/query/RangeQuery.html | 301 +
.../apache/kafka/streams/query/ResultOrder.html | 225 +
.../streams/query/StateQueryRequest.InStore.html | 139 +
.../kafka/streams/query/StateQueryRequest.html | 317 +
.../kafka/streams/query/StateQueryResult.html | 254 +
.../kafka/streams/query/TimestampedKeyQuery.html | 198 +
.../kafka/streams/query/TimestampedRangeQuery.html | 301 +
.../kafka/streams/query/VersionedKeyQuery.html | 214 +
.../apache/kafka/streams/query/WindowKeyQuery.html | 183 +
.../kafka/streams/query/WindowRangeQuery.html | 191 +
.../kafka/streams/query/package-summary.html | 189 +
.../apache/kafka/streams/query/package-tree.html | 106 +
...slStoreSuppliers.InMemoryDslStoreSuppliers.html | 201 +
...DslStoreSuppliers.RocksDBDslStoreSuppliers.html | 201 +
.../streams/state/BuiltInDslStoreSuppliers.html | 189 +
.../kafka/streams/state/DslKeyValueParams.html | 215 +
.../kafka/streams/state/DslSessionParams.html | 229 +
.../kafka/streams/state/DslStoreSuppliers.html | 192 +
.../kafka/streams/state/DslWindowParams.html | 279 +
.../org/apache/kafka/streams/state/HostInfo.html | 247 +
.../streams/state/KeyValueBytesStoreSupplier.html | 109 +
.../kafka/streams/state/KeyValueIterator.html | 168 +
.../apache/kafka/streams/state/KeyValueStore.html | 225 +
.../kafka/streams/state/QueryableStoreType.html | 176 +
.../QueryableStoreTypes.KeyValueStoreType.html | 178 +
.../QueryableStoreTypes.SessionStoreType.html | 178 +
.../state/QueryableStoreTypes.WindowStoreType.html | 178 +
.../kafka/streams/state/QueryableStoreTypes.html | 283 +
.../kafka/streams/state/ReadOnlyKeyValueStore.html | 310 +
.../kafka/streams/state/ReadOnlySessionStore.html | 666 +
.../kafka/streams/state/ReadOnlyWindowStore.html | 426 +
.../kafka/streams/state/RocksDBConfigSetter.html | 198 +
.../streams/state/SessionBytesStoreSupplier.html | 164 +
.../apache/kafka/streams/state/SessionStore.html | 424 +
.../apache/kafka/streams/state/StateSerdes.html | 443 +
.../apache/kafka/streams/state/StoreBuilder.html | 254 +
.../apache/kafka/streams/state/StoreSupplier.html | 173 +
.../org/apache/kafka/streams/state/Stores.html | 740 +
.../kafka/streams/state/TimestampedBytesStore.html | 122 +
.../streams/state/TimestampedKeyValueStore.html | 109 +
.../streams/state/TimestampedWindowStore.html | 116 +
.../kafka/streams/state/ValueAndTimestamp.html | 253 +
.../kafka/streams/state/VersionedBytesStore.html | 175 +
.../streams/state/VersionedBytesStoreSupplier.html | 151 +
.../streams/state/VersionedKeyValueStore.html | 343 +
.../kafka/streams/state/VersionedRecord.html | 252 +
.../streams/state/VersionedRecordIterator.html | 147 +
.../streams/state/WindowBytesStoreSupplier.html | 197 +
.../apache/kafka/streams/state/WindowStore.html | 552 +
.../kafka/streams/state/WindowStoreIterator.html | 152 +
.../kafka/streams/state/package-summary.html | 278 +
.../apache/kafka/streams/state/package-tree.html | 180 +
.../org/apache/kafka/streams/test/TestRecord.html | 440 +
.../apache/kafka/streams/test/package-summary.html | 120 +
.../apache/kafka/streams/test/package-tree.html | 71 +
41/javadoc/org/apache/kafka/tools/api/Decoder.html | 134 +
.../org/apache/kafka/tools/api/DefaultDecoder.html | 168 +
.../org/apache/kafka/tools/api/IntegerDecoder.html | 168 +
.../org/apache/kafka/tools/api/LongDecoder.html | 168 +
.../org/apache/kafka/tools/api/RecordReader.html | 179 +
.../org/apache/kafka/tools/api/StringDecoder.html | 168 +
.../apache/kafka/tools/api/package-summary.html | 114 +
.../org/apache/kafka/tools/api/package-tree.html | 94 +
41/javadoc/overview-summary.html | 25 +
41/javadoc/overview-tree.html | 1452 ++
41/javadoc/package-search-index.js | 1 +
41/javadoc/resources/glass.png | Bin 0 -> 499 bytes
41/javadoc/resources/x.png | Bin 0 -> 394 bytes
41/javadoc/script-dir/jquery-3.7.1.min.js | 2 +
41/javadoc/script-dir/jquery-ui.min.css | 6 +
41/javadoc/script-dir/jquery-ui.min.js | 6 +
41/javadoc/script.js | 132 +
41/javadoc/search.js | 354 +
41/javadoc/serialized-form.html | 2163 ++
41/javadoc/stylesheet.css | 869 +
41/javadoc/tag-search-index.js | 1 +
41/javadoc/type-search-index.js | 1 +
41/js/templateData.js | 24 +
41/ops.html | 4515 ++++
41/protocol.html | 239 +
41/quickstart.html | 354 +
41/security.html | 2494 ++
41/streams/architecture.html | 206 +
41/streams/core-concepts.html | 387 +
41/streams/developer-guide/app-reset-tool.html | 184 +
41/streams/developer-guide/config-streams.html | 1519 ++
41/streams/developer-guide/datatypes.html | 238 +
41/streams/developer-guide/dsl-api.html | 4363 ++++
.../developer-guide/dsl-topology-naming.html | 363 +
41/streams/developer-guide/index.html | 106 +
.../developer-guide/interactive-queries.html | 503 +
41/streams/developer-guide/manage-topics.html | 135 +
41/streams/developer-guide/memory-mgmt.html | 280 +
41/streams/developer-guide/processor-api.html | 628 +
41/streams/developer-guide/running-app.html | 188 +
41/streams/developer-guide/security.html | 190 +
41/streams/developer-guide/testing.html | 396 +
41/streams/developer-guide/write-streams.html | 224 +
41/streams/index.html | 355 +
41/streams/quickstart.html | 352 +
41/streams/tutorial.html | 608 +
41/streams/upgrade-guide.html | 1898 ++
41/toc.html | 241 +
41/upgrade.html | 502 +
41/uses.html | 81 +
41/zk2kraft-summary.html | 27 +
1286 files changed, 368820 insertions(+)
diff --git a/41/README.md b/41/README.md
new file mode 100644
index 000000000..a71c49a57
--- /dev/null
+++ b/41/README.md
@@ -0,0 +1,4 @@
+# Docs
+
+The documentation needs to run with [kafka-site](https://github.com/apache/kafka-site).
+Please check the README in the kafka-site repository to preview documentation locally.
diff --git a/41/api.html b/41/api.html
new file mode 100644
index 000000000..e35d79ca0
--- /dev/null
+++ b/41/api.html
@@ -0,0 +1,124 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<script id="api-template" type="text/x-handlebars-template">
+ Kafka includes five core apis:
+ <ol>
+ <li>The <a href="#producerapi">Producer</a> API allows applications to send streams of data to topics in the Kafka cluster.
+ <li>The <a href="#consumerapi">Consumer</a> API allows applications to read streams of data from topics in the Kafka cluster.
+ <li>The <a href="#streamsapi">Streams</a> API allows transforming streams of data from input topics to output topics.
+ <li>The <a href="#connectapi">Connect</a> API allows implementing connectors that continually pull from some source system or application into Kafka or push from Kafka into some sink system or application.
+ <li>The <a href="#adminapi">Admin</a> API allows managing and inspecting topics, brokers, and other Kafka objects.
+ </ol>
+
+ Kafka exposes all its functionality over a language independent protocol which has clients available in many programming languages. However only the Java clients are maintained as part of the main Kafka project, the others are available as independent open source projects. A list of non-Java clients is available <a href="https://cwiki.apache.org/confluence/x/3gDVAQ">here</a>.
+
+ <h3 class="anchor-heading"><a id="producerapi" class="anchor-link"></a><a href="#producerapi">2.1 Producer API</a></h3>
+
+ The Producer API allows applications to send streams of data to topics in the Kafka cluster.
+ <p>
+ Examples of using the producer are shown in the
+ <a href="/{{version}}/javadoc/index.html?org/apache/kafka/clients/producer/KafkaProducer.html" title="Kafka {{dotVersion}} Javadoc">javadocs</a>.
+ <p>
+ To use the producer, add the following Maven dependency to your project:
+
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-clients</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+
+ <h3 class="anchor-heading"><a id="consumerapi" class="anchor-link"></a><a href="#consumerapi">2.2 Consumer API</a></h3>
+
+ The Consumer API allows applications to read streams of data from topics in the Kafka cluster.
+ <p>
+ Examples of using the consumer are shown in the
+ <a href="/{{version}}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html" title="Kafka {{dotVersion}} Javadoc">javadocs</a>.
+ <p>
+ To use the consumer, add the following Maven dependency to your project:
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-clients</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+
+ <h3 class="anchor-heading"><a id="shareconsumerapi" class="anchor-link"></a><a href="#shareconsumerapi">2.3 Share Consumer API (Preview)</a></h3>
+
+ The Share Consumer API (Preview) enables applications within a share group to cooperatively consume and process data from Kafka topics.
+ <p>
+ Examples of using the share consumer are shown in the
+ <a href="/{{version}}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaShareConsumer.html" title="Kafka {{dotVersion}} Javadoc">javadocs</a>.
+ <p>
+ To use the share consumer, add the following Maven dependency to your project:
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-clients</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+
+ <h3 class="anchor-heading"><a id="streamsapi" class="anchor-link"></a><a href="#streamsapi">2.4 Streams API</a></h3>
+
+ The <a href="/{{version}}/documentation/streams">Streams</a> API allows transforming streams of data from input topics to output topics.
+ <p>
+ Examples of using this library are shown in the
+ <a href="/{{version}}/javadoc/index.html?org/apache/kafka/streams/KafkaStreams.html" title="Kafka {{dotVersion}} Javadoc">javadocs</a>.
+ <p>
+ Additional documentation on using the Streams API is available <a href="/{{version}}/documentation/streams">here</a>.
+ <p>
+ To use Kafka Streams, add the following Maven dependency to your project:
+
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-streams</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+
+ <p>
+ When using Scala you may optionally include the <code>kafka-streams-scala</code> library. Additional documentation on using the Kafka Streams DSL for Scala is available <a href="/{{version}}/documentation/streams/developer-guide/dsl-api.html#scala-dsl">in the developer guide</a>.
+ <p>
+ To use Kafka Streams DSL for Scala {{scalaVersion}}, add the following Maven dependency to your project:
+
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-streams-scala_{{scalaVersion}}</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+
+ <h3 class="anchor-heading"><a id="connectapi" class="anchor-link"></a><a href="#connectapi">2.5 Connect API</a></h3>
+
+ The Connect API allows implementing connectors that continually pull from some source data system into Kafka or push from Kafka into some sink data system.
+ <p>
+ Many users of Connect won't need to use this API directly, though, they can use pre-built connectors without needing to write any code. Additional information on using Connect is available <a href="/documentation.html#connect">here</a>.
+ <p>
+ Those who want to implement custom connectors can see the <a href="/{{version}}/javadoc/index.html?org/apache/kafka/connect" title="Kafka {{dotVersion}} Javadoc">javadoc</a>.
+ <p>
+
+ <h3 class="anchor-heading"><a id="adminapi" class="anchor-link"></a><a href="#adminapi">2.6 Admin API</a></h3>
+
+ The Admin API supports managing and inspecting topics, brokers, acls, and other Kafka objects.
+ <p>
+ To use the Admin API, add the following Maven dependency to your project:
+ <pre class="line-numbers"><code class="language-xml"><dependency>
+ <groupId>org.apache.kafka</groupId>
+ <artifactId>kafka-clients</artifactId>
+ <version>{{fullDotVersion}}</version>
+</dependency></code></pre>
+ For more information about the Admin APIs, see the <a href="/{{version}}/javadoc/index.html?org/apache/kafka/clients/admin/Admin.html" title="Kafka {{dotVersion}} Javadoc">javadoc</a>.
+ <p>
+
+</script>
+
+<div class="p-api"></div>
diff --git a/41/compatibility-summary.html b/41/compatibility-summary.html
new file mode 100644
index 000000000..bb6f2d581
--- /dev/null
+++ b/41/compatibility-summary.html
@@ -0,0 +1,27 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<script><!--#include virtual="js/templateData.js" --></script>
+
+<script id="compatibility-summary-template" type="text/x-handlebars-template">
+<p>
+ With the release of Kafka 4.0, significant changes have been introduced that impact compatibility across various
+ components. To assist users in planning upgrades and ensuring seamless interoperability, a comprehensive
+ <a href="/{{version}}/documentation/compatibility.html">compatibility matrix</a> has been prepared.
+</p>
+</script>
+<div class="p-compatibility-summary"></div>
diff --git a/41/configuration.html b/41/configuration.html
new file mode 100644
index 000000000..c06007151
--- /dev/null
+++ b/41/configuration.html
@@ -0,0 +1,442 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<script id="configuration-template" type="text/x-handlebars-template">
+ Kafka uses key-value pairs in the <a href="https://en.wikipedia.org/wiki/.properties">property file format</a> for configuration. These values can be supplied either from a file or programmatically.
+
+ <h3 class="anchor-heading"><a id="brokerconfigs" class="anchor-link"></a><a href="#brokerconfigs">3.1 Broker Configs</a></h3>
+
+ The essential configurations are the following:
+ <ul>
+ <li><code>node.id</code>
+ <li><code>log.dirs</code>
+ <li><code>process.roles</code>
+ <li><code>controller.quorum.bootstrap.servers</code>
+ </ul>
+
+ Topic configurations and defaults are discussed in more detail <a href="#topicconfigs">below</a>.
+
+ <!--#include virtual="generated/kafka_config.html" -->
+
+ <p>More details about broker configuration can be found in the scala class <code>kafka.server.KafkaConfig</code>.</p>
+
+ <h4 class="anchor-heading"><a id="dynamicbrokerconfigs" class="anchor-link"></a><a href="#dynamicbrokerconfigs">3.1.1 Updating Broker Configs</a></h4>
+ From Kafka version 1.1 onwards, some of the broker configs can be updated without restarting the broker. See the
+ <code>Dynamic Update Mode</code> column in <a href="#brokerconfigs">Broker Configs</a> for the update mode of each broker config.
+ <ul>
+ <li><code>read-only</code>: Requires a broker restart for update</li>
+ <li><code>per-broker</code>: May be updated dynamically for each broker</li>
+ <li><code>cluster-wide</code>: May be updated dynamically as a cluster-wide default. May also be updated as a per-broker value for testing.</li>
+ </ul>
+
+ To alter the current broker configs for broker id 0 (for example, the number of log cleaner threads):
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --add-config log.cleaner.threads=2</code></pre>
+
+ To describe the current dynamic broker configs for broker id 0:
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --describe</code></pre>
+
+ To delete a config override and revert to the statically configured or default value for broker id 0 (for example,
+ the number of log cleaner threads):
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --delete-config log.cleaner.threads</code></pre>
+
+ Some configs may be configured as a cluster-wide default to maintain consistent values across the whole cluster. All brokers
+ in the cluster will process the cluster default update. For example, to update log cleaner threads on all brokers:
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-default --alter --add-config log.cleaner.threads=2</code></pre>
+
+ To describe the currently configured dynamic cluster-wide default configs:
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-default --describe</code></pre>
+
+ All configs that are configurable at cluster level may also be configured at per-broker level (e.g. for testing).
+ If a config value is defined at different levels, the following order of precedence is used:
+ <ul>
+ <li>Dynamic per-broker config stored in the metadata log</li>
+ <li>Dynamic cluster-wide default config stored in the metadata log</li>
+ <li>Static broker config from <code>server.properties</code></li>
+ <li>Kafka default, see <a href="#brokerconfigs">broker configs</a></li>
+ </ul>
+
+ <h5>Updating SSL Keystore of an Existing Listener</h5>
+ Brokers may be configured with SSL keystores with short validity periods to reduce the risk of compromised certificates.
+ Keystores may be updated dynamically without restarting the broker. The config name must be prefixed with the listener prefix
+ <code>listener.name.{listenerName}.</code> so that only the keystore config of a specific listener is updated.
+ The following configs may be updated in a single alter request at per-broker level:
+ <ul>
+ <li><code>ssl.keystore.type</code></li>
+ <li><code>ssl.keystore.location</code></li>
+ <li><code>ssl.keystore.password</code></li>
+ <li><code>ssl.key.password</code></li>
+ </ul>
+ If the listener is the inter-broker listener, the update is allowed only if the new keystore is trusted by the truststore
+ configured for that listener. For other listeners, no trust validation is performed on the keystore by the broker. Certificates
+ must be signed by the same certificate authority that signed the old certificate to avoid any client authentication failures.
+
+ <h5>Updating SSL Truststore of an Existing Listener</h5>
+ Broker truststores may be updated dynamically without restarting the broker to add or remove certificates.
+ Updated truststore will be used to authenticate new client connections. The config name must be prefixed with the
+ listener prefix <code>listener.name.{listenerName}.</code> so that only the truststore config of a specific listener
+ is updated. The following configs may be updated in a single alter request at per-broker level:
+ <ul>
+ <li><code>ssl.truststore.type</code></li>
+ <li><code>ssl.truststore.location</code></li>
+ <li><code>ssl.truststore.password</code></li>
+ </ul>
+ If the listener is the inter-broker listener, the update is allowed only if the existing keystore for that listener is trusted by
+ the new truststore. For other listeners, no trust validation is performed by the broker before the update. Removal of CA certificates
+ used to sign client certificates from the new truststore can lead to client authentication failures.
+
+ <h5>Updating Default Topic Configuration</h5>
+ Default topic configuration options used by brokers may be updated without broker restart. The configs are applied to topics
+ without a topic config override for the equivalent per-topic config. One or more of these configs may be overridden at
+ cluster-default level used by all brokers.
+ <ul>
+ <li><code>log.segment.bytes</code></li>
+ <li><code>log.roll.ms</code></li>
+ <li><code>log.roll.hours</code></li>
+ <li><code>log.roll.jitter.ms</code></li>
+ <li><code>log.roll.jitter.hours</code></li>
+ <li><code>log.index.size.max.bytes</code></li>
+ <li><code>log.flush.interval.messages</code></li>
+ <li><code>log.flush.interval.ms</code></li>
+ <li><code>log.retention.bytes</code></li>
+ <li><code>log.retention.ms</code></li>
+ <li><code>log.retention.minutes</code></li>
+ <li><code>log.retention.hours</code></li>
+ <li><code>log.index.interval.bytes</code></li>
+ <li><code>log.cleaner.delete.retention.ms</code></li>
+ <li><code>log.cleaner.min.compaction.lag.ms</code></li>
+ <li><code>log.cleaner.max.compaction.lag.ms</code></li>
+ <li><code>log.cleaner.min.cleanable.ratio</code></li>
+ <li><code>log.cleanup.policy</code></li>
+ <li><code>log.segment.delete.delay.ms</code></li>
+ <li><code>unclean.leader.election.enable</code></li>
+ <li><code>min.insync.replicas</code></li>
+ <li><code>max.message.bytes</code></li>
+ <li><code>compression.type</code></li>
+ <li><code>log.preallocate</code></li>
+ <li><code>log.message.timestamp.type</code></li>
+ </ul>
+
+ <h5>Updating Log Cleaner Configs</h5>
+ Log cleaner configs may be updated dynamically at cluster-default level used by all brokers. The changes take effect
+ on the next iteration of log cleaning. One or more of these configs may be updated:
+ <ul>
+ <li><code>log.cleaner.threads</code></li>
+ <li><code>log.cleaner.io.max.bytes.per.second</code></li>
+ <li><code>log.cleaner.dedupe.buffer.size</code></li>
+ <li><code>log.cleaner.io.buffer.size</code></li>
+ <li><code>log.cleaner.io.buffer.load.factor</code></li>
+ <li><code>log.cleaner.backoff.ms</code></li>
+ </ul>
+
+ <h5>Updating Thread Configs</h5>
+ The size of various thread pools used by the broker may be updated dynamically at cluster-default level used by all brokers.
+ Updates are restricted to the range <code>currentSize / 2</code> to <code>currentSize * 2</code> to ensure that config updates are
+ handled gracefully.
+ <ul>
+ <li><code>num.network.threads</code></li>
+ <li><code>num.io.threads</code></li>
+ <li><code>num.replica.fetchers</code></li>
+ <li><code>num.recovery.threads.per.data.dir</code></li>
+ <li><code>log.cleaner.threads</code></li>
+ <li><code>background.threads</code></li>
+ <li><code>remote.log.reader.threads</code></li>
+ <li><code>remote.log.manager.copier.thread.pool.size</code></li>
+ <li><code>remote.log.manager.expiration.thread.pool.size</code></li>
+ </ul>
+
+ <h5>Updating ConnectionQuota Configs</h5>
+ The maximum number of connections allowed for a given IP/host by the broker may be updated dynamically at cluster-default level used by all brokers.
+ The changes will apply for new connection creations and the existing connections count will be taken into account by the new limits.
+ <ul>
+ <li><code>max.connections.per.ip</code></li>
+ <li><code>max.connections.per.ip.overrides</code></li>
+ </ul>
+
+ <h5>Adding and Removing Listeners</h5>
+ <p>Listeners may be added or removed dynamically. When a new listener is added, security configs of the listener must be provided
+ as listener configs with the listener prefix <code>listener.name.{listenerName}.</code>. If the new listener uses SASL,
+ the JAAS configuration of the listener must be provided using the JAAS configuration property <code>sasl.jaas.config</code>
+ with the listener and mechanism prefix. See <a href="#security_jaas_broker">JAAS configuration for Kafka brokers</a> for details.</p>
+
+ <p>In Kafka version 1.1.x, the listener used by the inter-broker listener may not be updated dynamically. To update the inter-broker
+ listener to a new listener, the new listener may be added on all brokers without restarting the broker. A rolling restart is then
+ required to update <code>inter.broker.listener.name</code>.</p>
+
+ In addition to all the security configs of new listeners, the following configs may be updated dynamically at per-broker level:
+ <ul>
+ <li><code>listeners</code></li>
+ <li><code>advertised.listeners</code></li>
+ <li><code>listener.security.protocol.map</code></li>
+ </ul>
+ Inter-broker listener must be configured using the static broker configuration <code>inter.broker.listener.name</code>
+ or <code>security.inter.broker.protocol</code>.
+
+ <h3 class="anchor-heading"><a id="topicconfigs" class="anchor-link"></a><a href="#topicconfigs">3.2 Topic Configs</a></h3>
+
+ Configurations pertinent to topics have both a server default as well an optional per-topic override. If no per-topic configuration is given the server default is used. The override can be set at topic creation time by giving one or more <code>--config</code> options. This example creates a topic named <i>my-topic</i> with a custom max message size and flush rate:
+ <pre><code class="language-bash">$ bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --topic my-topic --partitions 1 \
+ --replication-factor 1 --config max.message.bytes=64000 --config flush.messages=1</code></pre>
+ Overrides can also be changed or set later using the alter configs command. This example updates the max message size for <i>my-topic</i>:
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type topics --entity-name my-topic
+ --alter --add-config max.message.bytes=128000</code></pre>
+
+ To check overrides set on the topic you can do
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type topics --entity-name my-topic --describe</code></pre>
+
+ To remove an override you can do
+ <pre><code class="language-bash">$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type topics --entity-name my-topic
+ --alter --delete-config max.message.bytes</code></pre>
+
+ Below is the topic configuration. The server's default configuration for this property is given under the Server Default Property heading. A given server default config value only applies to a topic if it does not have an explicit topic config override.
+
+ <!--#include virtual="generated/topic_config.html" -->
+
+ <h3 class="anchor-heading"><a id="groupconfigs" class="anchor-link"></a><a href="#groupconfigs">3.3 Group Configs</a></h3>
+
+ Below is the group configuration:
+ <!--#include virtual="generated/group_config.html" -->
+
+ <h3 class="anchor-heading"><a id="producerconfigs" class="anchor-link"></a><a href="#producerconfigs">3.4 Producer Configs</a></h3>
+
+ Below is the producer configuration:
+ <!--#include virtual="generated/producer_config.html" -->
+
+ <h3 class="anchor-heading"><a id="consumerconfigs" class="anchor-link"></a><a href="#consumerconfigs">3.5 Consumer Configs</a></h3>
+
+ Below is the consumer and share consumer configuration:
+ <!--#include virtual="generated/consumer_config.html" -->
+
+ <h3 class="anchor-heading"><a id="connectconfigs" class="anchor-link"></a><a href="#connectconfigs">3.6 Kafka Connect Configs</a></h3>
+ Below is the Kafka Connect framework configuration.
+ <!--#include virtual="generated/connect_config.html" -->
+
+ <h4 class="anchor-heading"><a id="sourceconnectconfigs" class="anchor-link"></a><a href="#sourceconnectconfigs">3.6.1 Source Connector Configs</a></h4>
+ Below is the source connector configuration.
+ <!--#include virtual="generated/source_connector_config.html" -->
+
+ <h4 class="anchor-heading"><a id="sinkconnectconfigs" class="anchor-link"></a><a href="#sinkconnectconfigs">3.6.2 Sink Connector Configs</a></h4>
+ Below is the sink connector configuration.
+ <!--#include virtual="generated/sink_connector_config.html" -->
+
+ <h3 class="anchor-heading"><a id="streamsconfigs" class="anchor-link"></a><a href="#streamsconfigs">3.7 Kafka Streams Configs</a></h3>
+ Below is the Kafka Streams client library configuration.
+ <!--#include virtual="generated/streams_config.html" -->
+
+ <h3 class="anchor-heading"><a id="adminclientconfigs" class="anchor-link"></a><a href="#adminclientconfigs">3.8 Admin Configs</a></h3>
+ Below is the Kafka Admin client library configuration.
+ <!--#include virtual="generated/admin_client_config.html" -->
+
+ <h3 class="anchor-heading"><a id="mirrormakerconfigs" class="anchor-link"></a><a href="#mirrormakerconfigs">3.9 MirrorMaker Configs</a></h3>
+ Below is the configuration of the connectors that make up MirrorMaker 2.
+
+ <h4 class="anchor-heading"><a id="mirrormakercommonconfigs" class="anchor-link"></a><a href="#mirrormakercommonconfigs">3.9.1 MirrorMaker Common Configs</a></h4>
+ Below is the common configuration that applies to all three connectors.
+ <!--#include virtual="generated/mirror_connector_config.html" -->
+
+ <h4 class="anchor-heading"><a id="mirrormakersourceconfigs" class="anchor-link"></a><a href="#mirrormakersourceconfigs">3.9.2 MirrorMaker Source Configs</a></h4>
+ Below is the configuration of MirrorMaker 2 source connector for replicating topics.
+ <!--#include virtual="generated/mirror_source_config.html" -->
+
+ <h4 class="anchor-heading"><a id="mirrormakercheckpointconfigs" class="anchor-link"></a><a href="#mirrormakercheckpointconfigs">3.9.3 MirrorMaker Checkpoint Configs</a></h4>
+ Below is the configuration of MirrorMaker 2 checkpoint connector for emitting consumer offset checkpoints.
+ <!--#include virtual="generated/mirror_checkpoint_config.html" -->
+
+ <h4 class="anchor-heading"><a id="mirrormakerheartbeatconfigs" class="anchor-link"></a><a href="#mirrormakerheartbeatconfigs">3.9.4 MirrorMaker HeartBeat Configs</a></h4>
+ Below is the configuration of MirrorMaker 2 heartbeat connector for checking connectivity between connectors and clusters.
+ <!--#include virtual="generated/mirror_heartbeat_config.html" -->
+
+ <h3 class="anchor-heading"><a id="systemproperties" class="anchor-link"></a><a href="#systemproperties">3.10 System Properties</a></h3>
+ Kafka supports some configuration that can be enabled through Java system properties. System properties are usually set by passing the -D flag to the Java virtual machine in which Kafka components are running.
+ Below are the supported system properties.
+ <ul class="config-list">
+ <li>
+ <h4><a id="org.apache.kafka.sasl.oauthbearer.allowed.files"></a><a id="systemproperties_org.apache.kafka.sasl.oauthbearer.allowed.files" href="#systemproperties_org.apache.kafka.sasl.oauthbearer.allowed.files">org.apache.kafka.sasl.oauthbearer.allowed.files</a></h4>
+ <p>This system property is used to determine which files, if any, are allowed to be read by the SASL OAUTHBEARER plugin. This property accepts comma-separated list of files. By default the value is an empty list.
+ <p>If users want to enable some files, users need to explicitly set the system property like below.
+ <p><pre><code class="language-bash">-Dorg.apache.kafka.sasl.oauthbearer.allowed.files=/tmp/token,/tmp/private_key.pem</code></pre>
+ <table><tbody>
+ <tr><th>Since:</th><td>4.1.0</td></tr>
+ <tr><th>Default Value:</th><td></td></tr>
+ </tbody></table>
+ </li>
+ <li>
+ <h4><a id="org.apache.kafka.sasl.oauthbearer.allowed.urls"></a><a id="systemproperties_org.apache.kafka.sasl.oauthbearer.allowed.urls" href="#systemproperties_org.apache.kafka.sasl.oauthbearer.allowed.urls">org.apache.kafka.sasl.oauthbearer.allowed.urls</a></h4>
+ <p>This system property is used to set the allowed URLs as SASL OAUTHBEARER token or jwks endpoints. This property accepts comma-separated list of URLs. By default the value is an empty list.
+ <p>If users want to enable some URLs, users need to explicitly set the system property like below.
+ <p><pre><code class="language-bash">-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls=https://www.example.com,file:///tmp/token</code></pre>
+ <table><tbody>
+ <tr><th>Since:</th><td>4.0.0</td></tr>
+ <tr><th>Default Value:</th><td></td></tr>
+ </tbody></table>
+ </li>
+ <li>
+ <h4><a id="org.apache.kafka.disallowed.login.modules"></a><a id="systemproperties_org.apache.kafka.disallowed.login.modules" href="#systemproperties_org.apache.kafka.disallowed.login.modules">org.apache.kafka.disallowed.login.modules</a></h4>
+ <p>This system property is used to disable the problematic login modules usage in SASL JAAS configuration. This property accepts comma-separated list of loginModule names. By default <b>com.sun.security.auth.module.JndiLoginModule</b> loginModule is disabled.
+ <p>If users want to enable JndiLoginModule, users need to explicitly reset the system property like below. We advise the users to validate configurations and only allow trusted JNDI configurations. For more details <a href="https://kafka.apache.org/cve-list#CVE-2023-25194">CVE-2023-25194</a>.
+ <p><pre><code class="language-bash">-Dorg.apache.kafka.disallowed.login.modules=</code></pre>
+ <p>To disable more loginModules, update the system property with comma-separated loginModule names. Make sure to explicitly add <b>JndiLoginModule</b> module name to the comma-separated list like below.
+ <p><pre><code class="language-bash">-Dorg.apache.kafka.disallowed.login.modules=com.sun.security.auth.module.JndiLoginModule,com.ibm.security.auth.module.LdapLoginModule,com.ibm.security.auth.module.Krb5LoginModule</code></pre>
+ <table><tbody>
+ <tr><th>Since:</th><td>3.4.0</td></tr>
+ <tr><th>Default Value:</th><td>com.sun.security.auth.module.JndiLoginModule</td></tr>
+ </tbody></table>
+ </li>
+ <li>
+ <h4><a id="org.apache.kafka.automatic.config.providers"></a><a id="systemproperties_org.apache.kafka.automatic.config.providers" href="#systemproperties_org.apache.kafka.automatic.config.providers">org.apache.kafka.automatic.config.providers</a></h4>
+ <p>This system property controls the automatic loading of ConfigProvider implementations in Apache Kafka. ConfigProviders are used to dynamically supply configuration values from sources such as files, directories, or environment variables. This property accepts a comma-separated list of ConfigProvider names. By default, all built-in ConfigProviders are enabled, including <b>FileConfigProvider</b>, <b>DirectoryConfigProvider</b>, and <b>EnvVarConfigProvider</b>.</p>
+ <p>If users want to disable all automatic ConfigProviders, they need to explicitly set the system property as shown below. Disabling automatic ConfigProviders is recommended in environments where configuration data comes from untrusted sources or where increased security is required. For more details, see <a href="https://kafka.apache.org/cve-list#CVE-2024-31141">CVE-2024-31141</a>.</p>
+ <pre><code class="language-bash">-Dorg.apache.kafka.automatic.config.providers=none</code></pre>
+ <p>To allow specific ConfigProviders, update the system property with a comma-separated list of fully qualified ConfigProvider class names. For example, to enable only the <b>EnvVarConfigProvider</b>, set the property as follows:</p>
+ <pre><code class="language-bash">-Dorg.apache.kafka.automatic.config.providers=org.apache.kafka.common.config.provider.EnvVarConfigProvider</code></pre>
+ <p>To use multiple ConfigProviders, include their names in a comma-separated list as shown below:</p>
+ <pre><code class="language-bash">-Dorg.apache.kafka.automatic.config.providers=org.apache.kafka.common.config.provider.FileConfigProvider,org.apache.kafka.common.config.provider.EnvVarConfigProvider</code></pre>
+ <table>
+ <tbody>
+ <tr><th>Since:</th><td>3.8.0</td></tr>
+ <tr><th>Default Value:</th><td>All built-in ConfigProviders are enabled</td></tr>
+ </tbody>
+ </table>
+ </li>
+ </ul>
+
+ <h3 class="anchor-heading"><a id="tieredstorageconfigs" class="anchor-link"></a><a href="#tieredstorageconfigs">3.11 Tiered Storage Configs</a></h3>
+ Below is the Tiered Storage configuration.
+ <!--#include virtual="generated/remote_log_manager_config.html" -->
+ <!--#include virtual="generated/remote_log_metadata_manager_config.html" -->
+
+ <h3 class="anchor-heading">
+ <a id="config_providers" class="anchor-link"></a>
+ <a href="#config_providers">3.12 Configuration Providers</a>
+ </h3>
+
+ <p>
+ Use configuration providers to load configuration data from external sources. This might include sensitive information, such as passwords, API keys, or other credentials.
+ </p>
+
+ <p>You have the following options:</p>
+ <ul>
+ <li>
+ Use a custom provider by creating a class implementing the
+ <a href="/{{version}}/javadoc/org/apache/kafka/common/config/provider/ConfigProvider.html"><code>ConfigProvider</code></a> interface and packaging it into a JAR file.
+ </li>
+ <li>Use a built-in provider:</li>
+ <ul>
+ <li><a href="/{{version}}/javadoc/org/apache/kafka/common/config/provider/DirectoryConfigProvider.html"><code>DirectoryConfigProvider</code></a></li>
+ <li><a href="/{{version}}/javadoc/org/apache/kafka/common/config/provider/EnvVarConfigProvider.html"><code>EnvVarConfigProvider</code></a></li>
+ <li><a href="/{{version}}/javadoc/org/apache/kafka/common/config/provider/FileConfigProvider.html"><code>FileConfigProvider</code></a></li>
+ </ul>
+ </ul>
+
+ <p>
+ To use a configuration provider, specify it in your configuration using the <code>config.providers</code> property.
+ </p>
+
+ <h4 class="anchor-heading">
+ <a id="using_config_providers" class="anchor-link"></a>
+ <a href="#using_config_providers">Using Configuration Providers</a>
+ </h4>
+ <p>Configuration providers allow you to pass parameters and retrieve configuration data from various sources.</p>
+ <p>To specify configuration providers, you use a comma-separated list of aliases and the fully-qualified class names that implement the configuration providers:</p>
+ <pre><code>config.providers=provider1,provider2
+config.providers.provider1.class=com.example.Provider1
+config.providers.provider2.class=com.example.Provider2</code></pre>
+ <p>Each provider can have its own set of parameters, which are passed in a specific format:</p>
+ <pre><code>config.providers.<provider_alias>.param.<name>=<value></code></pre>
+ <p>The <code>ConfigProvider</code> interface serves as a base for all configuration providers.
+ Custom implementations of this interface can be created to retrieve configuration data from various sources.
+ You can package the implementation as a JAR file, add the JAR to your classpath, and reference the provider's class in your configuration.</p>
+ <p><b>Example custom provider configuration</b></p>
+ <pre><code>config.providers=customProvider
+config.providers.customProvider.class=com.example.customProvider
+config.providers.customProvider.param.param1=value1
+config.providers.customProvider.param.param2=value2</code></pre>
+
+ <h4 class="anchor-heading">
+ <a id="directory_config_provider" class="anchor-link"></a>
+ <a href="#directory_config_provider">DirectoryConfigProvider</a>
+ </h4>
+ <p>The <code>DirectoryConfigProvider</code> retrieves configuration data from files stored in a specified directory.</p>
+ <p>Each file represents a key, and its content is the value. This provider is useful for loading multiple configuration files and for organizing configuration data into separate files.</p>
+ <p>To restrict the files that the <code>DirectoryConfigProvider</code> can access, use the <code>allowed.paths</code> parameter.
+ This parameter accepts a comma-separated list of paths that the provider is allowed to access. If not set, all paths are allowed.</p>
+ <p><b>Example <code>DirectoryConfigProvider</code> configuration</b></p>
+<pre><code>config.providers=dirProvider
+config.providers.dirProvider.class=org.apache.kafka.common.config.provider.DirectoryConfigProvider
+config.providers.dirProvider.param.allowed.paths=/path/to/dir1,/path/to/dir2</code></pre>
+ <p>
+ To reference a value supplied by the <code>DirectoryConfigProvider</code>, use the correct placeholder syntax:
+ </p>
+<pre><code>${dirProvider:<path_to_file>:<file_name>}</code></pre>
+
+ <h4 class="anchor-heading">
+ <a id="env_var_config_provider" class="anchor-link"></a>
+ <a href="#env_var_config_provider">EnvVarConfigProvider</a>
+ </h4>
+ <p>The <code>EnvVarConfigProvider</code> retrieves configuration data from environment variables.</p>
+ <p>No specific parameters are required, as it reads directly from the specified environment variables.</p>
+ <p>This provider is useful for configuring applications running in containers, for example, to load certificates or JAAS configuration from environment variables mapped from secrets.</p>
+ <p>To restrict which environment variables the <code>EnvVarConfigProvider</code> can access, use the <code>allowlist.pattern</code> parameter. This parameter accepts a regular expression that environment variable names must match to be used by the provider.</p>
+ <p><b>Example <code>EnvVarConfigProvider</code> configuration</b></p>
+<pre><code>config.providers=envVarProvider
+config.providers.envVarProvider.class=org.apache.kafka.common.config.provider.EnvVarConfigProvider
+config.providers.envVarProvider.param.allowlist.pattern=^MY_ENVAR1_.*</code></pre>
+ <p>
+ To reference a value supplied by the <code>EnvVarConfigProvider</code>, use the correct placeholder syntax:
+ </p>
+<pre><code>${envVarProvider:<enVar_name>}</code></pre>
+
+ <h4 class="anchor-heading">
+ <a id="file_config_provider" class="anchor-link"></a>
+ <a href="#file_config_provider">FileConfigProvider</a>
+ </h4>
+ <p>The <code>FileConfigProvider</code> retrieves configuration data from a single properties file.</p>
+ <p>This provider is useful for loading configuration data from mounted files.</p>
+ <p>To restrict the file paths that the <code>FileConfigProvider</code> can access, use the <code>allowed.paths</code> parameter. This parameter accepts a comma-separated list of paths that the provider is allowed to access. If not set, all paths are allowed.</p>
+ <p><b>Example <code>FileConfigProvider</code> configuration</b></p>
+<pre><code>config.providers=fileProvider
+config.providers.fileProvider.class=org.apache.kafka.common.config.provider.FileConfigProvider
+config.providers.fileProvider.param.allowed.paths=/path/to/config1,/path/to/config2</code></pre>
+ <p>
+ To reference a value supplied by the <code>FileConfigProvider</code>, use the correct placeholder syntax:
+ </p>
+<pre><code>${fileProvider:<path_and_filename>:<property>}</code></pre>
+
+ <h4 class="anchor-heading">
+ <a id="ref_config_provider" class="anchor-link"></a>
+ <a href="#ref_config_provider">Example: Referencing files</a>
+ </h4>
+ <p>
+ Here’s an example that uses a file configuration provider with Kafka Connect to provide authentication credentials to a database for a connector.
+ </p>
+ <p>
+ First, create a <code>connector-credentials.properties</code> configuration file with the following credentials:
+ </p>
+ <pre><code>dbUsername=my-username
+dbPassword=my-password</code></pre>
+ <p>
+ Specify a <code>FileConfigProvider</code> in the Kafka Connect configuration:
+ </p>
+ <p><b>Example Kafka Connect configuration with a <code>FileConfigProvider</code></b></p>
+ <pre><code>config.providers=fileProvider
+config.providers.fileProvider.class=org.apache.kafka.common.config.provider.FileConfigProvider</code></pre>
+ <p>Next, reference the properties from the file in the connector configuration.</p>
+ <p><b>Example connector configuration referencing file properties</b></p>
+ <pre><code>database.user=${fileProvider:/path/to/connector-credentials.properties:dbUsername}
+database.password=${fileProvider:/path/to/connector-credentials.properties:dbPassword}</code></pre>
+ <p>At runtime, the configuration provider reads and extracts the values from the properties file.</p>
+</script>
+<div class="p-configuration"></div>
diff --git a/41/connect.html b/41/connect.html
new file mode 100644
index 000000000..457bc575e
--- /dev/null
+++ b/41/connect.html
@@ -0,0 +1,1056 @@
+<!--~
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~-->
+
+<script id="connect-template" type="text/x-handlebars-template">
+ <h3><a id="connect_overview" href="#connect_overview">8.1 Overview</a></h3>
+
+ <p>Kafka Connect is a tool for scalably and reliably streaming data between Apache Kafka and other systems. It makes it simple to quickly define <i>connectors</i> that move large collections of data into and out of Kafka. Kafka Connect can ingest entire databases or collect metrics from all your application servers into Kafka topics, making the data available for stream processing with low latency. An export job can deliver data from Kafka topics into secondary storage and query syst [...]
+
+ <p>Kafka Connect features include:</p>
+ <ul>
+ <li><b>A common framework for Kafka connectors</b> - Kafka Connect standardizes integration of other data systems with Kafka, simplifying connector development, deployment, and management</li>
+ <li><b>Distributed and standalone modes</b> - scale up to a large, centrally managed service supporting an entire organization or scale down to development, testing, and small production deployments</li>
+ <li><b>REST interface</b> - submit and manage connectors to your Kafka Connect cluster via an easy to use REST API</li>
+ <li><b>Automatic offset management</b> - with just a little information from connectors, Kafka Connect can manage the offset commit process automatically so connector developers do not need to worry about this error prone part of connector development</li>
+ <li><b>Distributed and scalable by default</b> - Kafka Connect builds on the existing group management protocol. More workers can be added to scale up a Kafka Connect cluster.</li>
+ <li><b>Streaming/batch integration</b> - leveraging Kafka's existing capabilities, Kafka Connect is an ideal solution for bridging streaming and batch data systems</li>
+ </ul>
+
+ <h3><a id="connect_user" href="#connect_user">8.2 User Guide</a></h3>
+
+ <p>The <a href="../quickstart">quickstart</a> provides a brief example of how to run a standalone version of Kafka Connect. This section describes how to configure, run, and manage Kafka Connect in more detail.</p>
+
+ <h4><a id="connect_running" href="#connect_running">Running Kafka Connect</a></h4>
+
+ <p>Kafka Connect currently supports two modes of execution: standalone (single process) and distributed.</p>
+
+ <p>In standalone mode all work is performed in a single process. This configuration is simpler to setup and get started with and may be useful in situations where only one worker makes sense (e.g. collecting log files), but it does not benefit from some of the features of Kafka Connect such as fault tolerance. You can start a standalone process with the following command:</p>
+
+ <pre><code class="language-bash">$ bin/connect-standalone.sh config/connect-standalone.properties [connector1.properties connector2.json …]</code></pre>
+
+ <p>The first parameter is the configuration for the worker. This includes settings such as the Kafka connection parameters, serialization format, and how frequently to commit offsets. The provided example should work well with a local cluster running with the default configuration provided by <code>config/server.properties</code>. It will require tweaking to use with a different configuration or production deployment. All workers (both standalone and distributed) require a few configs:</p>
+ <ul>
+ <li><code>bootstrap.servers</code> - List of Kafka servers used to bootstrap connections to Kafka</li>
+ <li><code>key.converter</code> - Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</li>
+ <li><code>value.converter</code> - Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</li>
+ <li><code>plugin.path</code> (default <code>empty</code>) - a list of paths that contain Connect plugins (connectors, converters, transformations). Before running quick starts, users must add the absolute path that contains the example FileStreamSourceConnector and FileStreamSinkConnector packaged in <code>connect-file-"version".jar</code>, because these connectors are not included by default to the <code>CLASSPATH</code> or the <code>plugin.path</code> of the Connect worker (see [...]
+ </ul>
+
+ <p>The important configuration options specific to standalone mode are:</p>
+ <ul>
+ <li><code>offset.storage.file.filename</code> - File to store source connector offsets</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 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 [...]
+
+ <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. Each file may either be a Java Properties file or a JSON file containing an object with the same structure as the request body of either the <code>POST /connectors</code> endpoint or the <code>PUT /connectors/{name}/config</code> endpoint (see the <a href="/{{version}}/generated/connect_rest.yaml">OpenAPI documentation</a>). You may include as many as you want, but all will execute within the same process (on different th [...]
+
+ <p>Distributed mode handles automatic balancing of work, allows you to scale up (or down) dynamically, and offers fault tolerance both in the active tasks and for configuration and offset commit data. Execution is very similar to standalone mode:</p>
+
+ <pre><code class="language-bash">$ bin/connect-distributed.sh config/connect-distributed.properties</code></pre>
+
+ <p>The difference is in the class which is started and the configuration parameters which change how the Kafka Connect process decides where to store configurations, how to assign work, and where to store offsets and task statues. In the distributed mode, Kafka Connect stores the offsets, configs and task statuses in Kafka topics. It is recommended to manually create the topics for offset, configs and statuses in order to achieve the desired the number of partitions and replication f [...]
+
+ <p>In particular, the following configuration parameters, in addition to the common settings mentioned above, are critical to set before starting your cluster:</p>
+ <ul>
+ <li><code>group.id</code> (default <code>connect-cluster</code>) - unique name for the cluster, used in forming the Connect cluster group; note that this <b>must not conflict</b> with consumer group IDs</li>
+ <li><code>config.storage.topic</code> (default <code>connect-configs</code>) - topic to use for storing connector and task configurations; note that this should be a single partition, highly replicated, compacted topic. You may need to manually create the topic to ensure the correct configuration as auto created topics may have multiple partitions or be automatically configured for deletion rather than compaction</li>
+ <li><code>offset.storage.topic</code> (default <code>connect-offsets</code>) - topic to use for storing offsets; this topic should have many partitions, be replicated, and be configured for compaction</li>
+ <li><code>status.storage.topic</code> (default <code>connect-status</code>) - topic to use for storing statuses; this topic can have multiple partitions, and should be replicated and configured for compaction</li>
+ </ul>
+
+ <p>Note that in distributed mode the connector configurations are not passed on the command line. Instead, use the REST API described below to create, modify, and destroy connectors.</p>
+
+
+ <h4><a id="connect_configuring" href="#connect_configuring">Configuring Connectors</a></h4>
+
+ <p>Connector configurations are simple key-value mappings. In both standalone and distributed mode, they are included in the JSON payload for the REST request that creates (or modifies) the connector. In standalone mode these can also be defined in a properties file and passed to the Connect process on the command line.</p>
+
+ <p>Most configurations are connector dependent, so they can't be outlined here. However, there are a few common options:</p>
+
+ <ul>
+ <li><code>name</code> - Unique name for the connector. Attempting to register again with the same name will fail.</li>
+ <li><code>connector.class</code> - The Java class for the connector</li>
+ <li><code>tasks.max</code> - The maximum number of tasks that should be created for this connector. The connector may create fewer tasks if it cannot achieve this level of parallelism.</li>
+ <li><code>key.converter</code> - (optional) Override the default key converter set by the worker.</li>
+ <li><code>value.converter</code> - (optional) Override the default value converter set by the worker.</li>
+ </ul>
+
+ <p>The <code>connector.class</code> config supports several formats: the full name or alias of the class for this connector. If the connector is org.apache.kafka.connect.file.FileStreamSinkConnector, you can either specify this full name or use FileStreamSink or FileStreamSinkConnector to make the configuration a bit shorter.</p>
+
+ <p>Sink connectors also have a few additional options to control their input. Each sink connector must set one of the following:</p>
+ <ul>
+ <li><code>topics</code> - A comma-separated list of topics to use as input for this connector</li>
+ <li><code>topics.regex</code> - A Java regular expression of topics to use as input for this connector</li>
+ </ul>
+
+ <p>For any other options, you should consult the documentation for the connector.</p>
+
+ <h4><a id="connect_transforms" href="#connect_transforms">Transformations</a></h4>
+
+ <p>Connectors can be configured with transformations to make lightweight message-at-a-time modifications. They can be convenient for data massaging and event routing.</p>
+
+ <p>A transformation chain can be specified in the connector configuration.</p>
+
+ <ul>
+ <li><code>transforms</code> - List of aliases for the transformation, specifying the order in which the transformations will be applied.</li>
+ <li><code>transforms.$alias.type</code> - Fully qualified class name for the transformation.</li>
+ <li><code>transforms.$alias.$transformationSpecificConfig</code> Configuration properties for the transformation</li>
+ </ul>
+
+ <p>For example, lets take the built-in file source connector and use a transformation to add a static field.</p>
+
+ <p>Throughout the example we'll use schemaless JSON data format. To use schemaless format, we changed the following two lines in <code>connect-standalone.properties</code> from true to false:</p>
+
+ <pre><code class="language-text">key.converter.schemas.enable
+value.converter.schemas.enable</code></pre>
+
+ <p>The file source connector reads each line as a String. We will wrap each line in a Map and then add a second field to identify the origin of the event. To do this, we use two transformations:</p>
+ <ul>
+ <li><b>HoistField</b> to place the input line inside a Map</li>
+ <li><b>InsertField</b> to add the static field. In this example we'll indicate that the record came from a file connector</li>
+ </ul>
+
+ <p>After adding the transformations, <code>connect-file-source.properties</code> file looks as following:</p>
+
+ <pre><code class="language-text">name=local-file-source
+connector.class=FileStreamSource
+tasks.max=1
+file=test.txt
+topic=connect-test
+transforms=MakeMap, InsertSource
+transforms.MakeMap.type=org.apache.kafka.connect.transforms.HoistField$Value
+transforms.MakeMap.field=line
+transforms.InsertSource.type=org.apache.kafka.connect.transforms.InsertField$Value
+transforms.InsertSource.static.field=data_source
+transforms.InsertSource.static.value=test-file-source</code></pre>
+
+ <p>All the lines starting with <code>transforms</code> were added for the transformations. You can see the two transformations we created: "InsertSource" and "MakeMap" are aliases that we chose to give the transformations. The transformation types are based on the list of built-in transformations you can see below. Each transformation type has additional configuration: HoistField requires a configuration called "field", which is the name of the field in the map that will include the [...]
+
+ <p>When we ran the file source connector on my sample file without the transformations, and then read them using <code>kafka-console-consumer.sh</code>, the results were:</p>
+
+ <pre><code class="language-text">"foo"
+"bar"
+"hello world"</code></pre>
+
+ <p>We then create a new file connector, this time after adding the transformations to the configuration file. This time, the results will be:</p>
+
+ <pre><code class="language-json">{"line":"foo","data_source":"test-file-source"}
+{"line":"bar","data_source":"test-file-source"}
+{"line":"hello world","data_source":"test-file-source"}</code></pre>
+
+ <p>You can see that the lines we've read are now part of a JSON map, and there is an extra field with the static value we specified. This is just one example of what you can do with transformations.</p>
+
+ <h5><a id="connect_included_transformation" href="#connect_included_transformation">Included transformations</a></h5>
+
+ <p>Several widely-applicable data and routing transformations are included with Kafka Connect:</p>
+
+ <ul>
+ <li><a href="#org.apache.kafka.connect.transforms.Cast">Cast</a> - Cast fields or the entire key or value to a specific type</li>
+ <li><a href="#org.apache.kafka.connect.transforms.DropHeaders">DropHeaders</a> - Remove headers by name</li>
+ <li><a href="#org.apache.kafka.connect.transforms.ExtractField">ExtractField</a> - Extract a specific field from Struct and Map and include only this field in results</li>
+ <li><a href="#org.apache.kafka.connect.transforms.Filter">Filter</a> - Removes messages from all further processing. This is used with a <a href="#connect_predicates">predicate</a> to selectively filter certain messages</li>
+ <li><a href="#org.apache.kafka.connect.transforms.Flatten">Flatten</a> - Flatten a nested data structure</li>
+ <li><a href="#org.apache.kafka.connect.transforms.HeaderFrom">HeaderFrom</a> - Copy or move fields in the key or value to the record headers</li>
+ <li><a href="#org.apache.kafka.connect.transforms.HoistField">HoistField</a> - Wrap the entire event as a single field inside a Struct or a Map</li>
+ <li><a href="#org.apache.kafka.connect.transforms.InsertField">InsertField</a> - Add a field using either static data or record metadata</li>
+ <li><a href="#org.apache.kafka.connect.transforms.InsertHeader">InsertHeader</a> - Add a header using static data</li>
+ <li><a href="#org.apache.kafka.connect.transforms.MaskField">MaskField</a> - Replace field with valid null value for the type (0, empty string, etc) or custom replacement (non-empty string or numeric value only)</li>
+ <li><a href="#org.apache.kafka.connect.transforms.RegexRouter">RegexRouter</a> - modify the topic of a record based on original topic, replacement string and a regular expression</li>
+ <li><a href="#org.apache.kafka.connect.transforms.ReplaceField">ReplaceField</a> - Filter or rename fields</li>
+ <li><a href="#org.apache.kafka.connect.transforms.SetSchemaMetadata">SetSchemaMetadata</a> - modify the schema name or version</li>
+ <li><a href="#org.apache.kafka.connect.transforms.TimestampConverter">TimestampConverter</a> - Convert timestamps between different formats</li>
+ <li><a href="#org.apache.kafka.connect.transforms.TimestampRouter">TimestampRouter</a> - Modify the topic of a record based on original topic and timestamp. Useful when using a sink that needs to write to different tables or indexes based on timestamps</li>
+ <li><a href="#org.apache.kafka.connect.transforms.ValueToKey">ValueToKey</a> - Replace the record key with a new key formed from a subset of fields in the record value</li>
+ </ul>
+
+ <p>Details on how to configure each transformation are listed below:</p>
+
+
+ <!--#include virtual="generated/connect_transforms.html" -->
+
+
+ <h5><a id="connect_predicates" href="#connect_predicates">Predicates</a></h5>
+
+ <p>Transformations can be configured with predicates so that the transformation is applied only to messages which satisfy some condition. In particular, when combined with the <b>Filter</b> transformation predicates can be used to selectively filter out certain messages.</p>
+
+ <p>Predicates are specified in the connector configuration.</p>
+
+ <ul>
+ <li><code>predicates</code> - Set of aliases for the predicates to be applied to some of the transformations.</li>
+ <li><code>predicates.$alias.type</code> - Fully qualified class name for the predicate.</li>
+ <li><code>predicates.$alias.$predicateSpecificConfig</code> - Configuration properties for the predicate.</li>
+ </ul>
+
+ <p>All transformations have the implicit config properties <code>predicate</code> and <code>negate</code>. A predicular predicate is associated with a transformation by setting the transformation's <code>predicate</code> config to the predicate's alias. The predicate's value can be reversed using the <code>negate</code> configuration property.</p>
+
+ <p>For example, suppose you have a source connector which produces messages to many different topics and you want to:</p>
+ <ul>
+ <li>filter out the messages in the 'foo' topic entirely</li>
+ <li>apply the ExtractField transformation with the field name 'other_field' to records in all topics <i>except</i> the topic 'bar'</li>
+ </ul>
+
+ <p>To do this we need first to filter out the records destined for the topic 'foo'. The Filter transformation removes records from further processing, and can use the TopicNameMatches predicate to apply the transformation only to records in topics which match a certain regular expression. TopicNameMatches's only configuration property is <code>pattern</code> which is a Java regular expression for matching against the topic name. The configuration would look like this:</p>
+
+ <pre><code class="language-text">transforms=Filter
+transforms.Filter.type=org.apache.kafka.connect.transforms.Filter
+transforms.Filter.predicate=IsFoo
+
+predicates=IsFoo
+predicates.IsFoo.type=org.apache.kafka.connect.transforms.predicates.TopicNameMatches
+predicates.IsFoo.pattern=foo</code></pre>
+
+ <p>Next we need to apply ExtractField only when the topic name of the record is not 'bar'. We can't just use TopicNameMatches directly, because that would apply the transformation to matching topic names, not topic names which do <i>not</i> match. The transformation's implicit <code>negate</code> config properties allows us to invert the set of records which a predicate matches. Adding the configuration for this to the previous example we arrive at:</p>
+
+ <pre><code class="language-text">transforms=Filter,Extract
+transforms.Filter.type=org.apache.kafka.connect.transforms.Filter
+transforms.Filter.predicate=IsFoo
+
+transforms.Extract.type=org.apache.kafka.connect.transforms.ExtractField$Key
+transforms.Extract.field=other_field
+transforms.Extract.predicate=IsBar
+transforms.Extract.negate=true
+
+predicates=IsFoo,IsBar
+predicates.IsFoo.type=org.apache.kafka.connect.transforms.predicates.TopicNameMatches
+predicates.IsFoo.pattern=foo
+
+predicates.IsBar.type=org.apache.kafka.connect.transforms.predicates.TopicNameMatches
+predicates.IsBar.pattern=bar</code></pre>
+
+ <p>Kafka Connect includes the following predicates:</p>
+
+ <ul>
+ <li><code>TopicNameMatches</code> - matches records in a topic with a name matching a particular Java regular expression.</li>
+ <li><code>HasHeaderKey</code> - matches records which have a header with the given key.</li>
+ <li><code>RecordIsTombstone</code> - matches tombstone records, that is records with a null value.</li>
+ </ul>
+
+ <p>Details on how to configure each predicate are listed below:</p>
+
+ <!--#include virtual="generated/connect_predicates.html" -->
+
+
+ <h4><a id="connect_rest" href="#connect_rest">REST API</a></h4>
+
+ <p>Since Kafka Connect is intended to be run as a service, it also provides a REST API for managing connectors. This REST API is available in both standalone and distributed mode. The REST API server can be configured using the <code>listeners</code> configuration option.
+ This field should contain a list of listeners in the following format: <code>protocol://host:port,protocol2://host2:port2</code>. Currently supported protocols are <code>http</code> and <code>https</code>.
+ For example:</p>
+
+ <pre><code class="language-text">listeners=http://localhost:8080,https://localhost:8443</code></pre>
+
+ <p>By default, if no <code>listeners</code> are specified, the REST server runs on port 8083 using the HTTP protocol. When using HTTPS, the configuration has to include the SSL configuration.
+ By default, it will use the <code>ssl.*</code> settings. In case it is needed to use different configuration for the REST API than for connecting to Kafka brokers, the fields can be prefixed with <code>listeners.https</code>.
+ When using the prefix, only the prefixed options will be used and the <code>ssl.*</code> options without the prefix will be ignored. Following fields can be used to configure HTTPS for the REST API:</p>
+
+ <ul>
+ <li><code>ssl.keystore.location</code></li>
+ <li><code>ssl.keystore.password</code></li>
+ <li><code>ssl.keystore.type</code></li>
+ <li><code>ssl.key.password</code></li>
+ <li><code>ssl.truststore.location</code></li>
+ <li><code>ssl.truststore.password</code></li>
+ <li><code>ssl.truststore.type</code></li>
+ <li><code>ssl.enabled.protocols</code></li>
+ <li><code>ssl.provider</code></li>
+ <li><code>ssl.protocol</code></li>
+ <li><code>ssl.cipher.suites</code></li>
+ <li><code>ssl.keymanager.algorithm</code></li>
+ <li><code>ssl.secure.random.implementation</code></li>
+ <li><code>ssl.trustmanager.algorithm</code></li>
+ <li><code>ssl.endpoint.identification.algorithm</code></li>
+ <li><code>ssl.client.auth</code></li>
+ </ul>
+
+ <p>The REST API is used not only by users to monitor / manage Kafka Connect. In distributed mode, it is also used for the Kafka Connect cross-cluster communication. Some requests received on the follower nodes REST API will be forwarded to the leader node REST API.
+ In case the URI under which is given host reachable is different from the URI which it listens on, the configuration options <code>rest.advertised.host.name</code>, <code>rest.advertised.port</code> and <code>rest.advertised.listener</code>
+ can be used to change the URI which will be used by the follower nodes to connect with the leader. When using both HTTP and HTTPS listeners, the <code>rest.advertised.listener</code> option can be also used to define which listener
+ will be used for the cross-cluster communication. When using HTTPS for communication between nodes, the same <code>ssl.*</code> or <code>listeners.https</code> options will be used to configure the HTTPS client.</p>
+
+ <p>The following are the currently supported REST API endpoints:</p>
+
+ <ul>
+ <li><code>GET /connectors</code> - return a list of active connectors</li>
+ <li><code>POST /connectors</code> - create a new connector; the request body should be a JSON object containing a string <code>name</code> field and an object <code>config</code> field with the connector configuration parameters. The JSON object may also optionally contain a string <code>initial_state</code> field which can take the following values - <code>STOPPED</code>, <code>PAUSED</code> or <code>RUNNING</code> (the default value)</li>
+ <li><code>GET /connectors/{name}</code> - get information about a specific connector</li>
+ <li><code>GET /connectors/{name}/config</code> - get the configuration parameters for a specific connector</li>
+ <li><code>PUT /connectors/{name}/config</code> - update the configuration parameters for a specific connector</li>
+ <li><code>PATCH /connectors/{name}/config</code> - patch the configuration parameters for a specific connector, where <code>null</code> values in the JSON body indicates removing of the key from the final configuration</li>
+ <li><code>GET /connectors/{name}/status</code> - get current status of the connector, including if it is running, failed, paused, etc., which worker it is assigned to, error information if it has failed, and the state of all its tasks</li>
+ <li><code>GET /connectors/{name}/tasks</code> - get a list of tasks currently running for a connector along with their configurations</li>
+ <li><code>GET /connectors/{name}/tasks/{taskid}/status</code> - get current status of the task, including if it is running, failed, paused, etc., which worker it is assigned to, and error information if it has failed</li>
+ <li><code>PUT /connectors/{name}/pause</code> - pause the connector and its tasks, which stops message processing until the connector is resumed. Any resources claimed by its tasks are left allocated, which allows the connector to begin processing data quickly once it is resumed.</li>
+ <li id="connect_stopconnector"><code>PUT /connectors/{name}/stop</code> - stop the connector and shut down its tasks, deallocating any resources claimed by its tasks. This is more efficient from a resource usage standpoint than pausing the connector, but can cause it to take longer to begin processing data once resumed. Note that the offsets for a connector can be only modified via the offsets management endpoints if it is in the stopped state</li>
+ <li><code>PUT /connectors/{name}/resume</code> - resume a paused or stopped connector (or do nothing if the connector is not paused or stopped)</li>
+ <li><code>POST /connectors/{name}/restart?includeTasks=<true|false>&onlyFailed=<true|false></code> - restart a connector and its tasks instances.
+ <ul>
+ <li>the "includeTasks" parameter specifies whether to restart the connector instance and task instances ("includeTasks=true") or just the connector instance ("includeTasks=false"), with the default ("false") preserving the same behavior as earlier versions.</li>
+ <li>the "onlyFailed" parameter specifies whether to restart just the instances with a FAILED status ("onlyFailed=true") or all instances ("onlyFailed=false"), with the default ("false") preserving the same behavior as earlier versions.</li>
+ </ul>
+ </li>
+ <li><code>POST /connectors/{name}/tasks/{taskId}/restart</code> - restart an individual task (typically because it has failed)</li>
+ <li><code>DELETE /connectors/{name}</code> - delete a connector, halting all tasks and deleting its configuration</li>
+ <li><code>GET /connectors/{name}/topics</code> - get the set of topics that a specific connector is using since the connector was created or since a request to reset its set of active topics was issued</li>
+ <li><code>PUT /connectors/{name}/topics/reset</code> - send a request to empty the set of active topics of a connector</li>
+ <li>Offsets management endpoints (see <a href="https://cwiki.apache.org/confluence/x/Io3GDQ">KIP-875</a> for more details):
+ <ul>
+ <li><code>GET /connectors/{name}/offsets</code> - get the current offsets for a connector</li>
+ <li><code>DELETE /connectors/{name}/offsets</code> - reset the offsets for a connector. The connector must exist and must be in the stopped state (see <a href="#connect_stopconnector"><code>PUT /connectors/{name}/stop</code></a>)</li>
+ <li><code>PATCH /connectors/{name}/offsets</code> - alter the offsets for a connector. The connector must exist and must be in the stopped state (see <a href="#connect_stopconnector"><code>PUT /connectors/{name}/stop</code></a>). The request body should be a JSON object containing a JSON array <code>offsets</code> field, similar to the response body of the <code>GET /connectors/{name}/offsets</code> endpoint.
+ An example request body for the <code>FileStreamSourceConnector</code>:
+ <pre><code class="language-json">{
+ "offsets": [
+ {
+ "partition": {
+ "filename": "test.txt"
+ },
+ "offset": {
+ "position": 30
+ }
+ }
+ ]
+}</code></pre>
+ An example request body for the <code>FileStreamSinkConnector</code>:
+ <pre><code class="language-json">{
+ "offsets": [
+ {
+ "partition": {
+ "kafka_topic": "test",
+ "kafka_partition": 0
+ },
+ "offset": {
+ "kafka_offset": 5
+ }
+ },
+ {
+ "partition": {
+ "kafka_topic": "test",
+ "kafka_partition": 1
+ },
+ "offset": null
+ }
+ ]
+}</code></pre>
+ The "offset" field may be null to reset the offset for a specific partition (applicable to both source and sink connectors). Note that the request body format depends on the connector implementation in the case of source connectors, whereas there is a common format across all sink connectors.</li>
+ </ul>
+ </li>
+ </ul>
+
+ <p>Kafka Connect also provides a REST API for getting information about connector plugins:</p>
+
+ <ul>
+ <li><code>GET /connector-plugins</code>- return a list of connector plugins installed in the Kafka Connect cluster. Note that the API only checks for connectors on the worker that handles the request, which means you may see inconsistent results, especially during a rolling upgrade if you add new connector jars</li>
+ <li><code>GET /connector-plugins/{plugin-type}/config</code> - get the configuration definition for the specified plugin.</li>
+ <li><code>PUT /connector-plugins/{connector-type}/config/validate</code> - validate the provided configuration values against the configuration definition. This API performs per config validation, returns suggested values and error messages during validation.</li>
+ </ul>
+
+ <p>The following is a supported REST request at the top-level (root) endpoint:</p>
+
+ <ul>
+ <li><code>GET /</code>- return basic information about the Kafka Connect cluster such as the version of the Connect worker that serves the REST request (including git commit ID of the source code) and the Kafka cluster ID that is connected to.
+ </ul>
+
+ <p>The <code>admin.listeners</code> configuration can be used to configure admin REST APIs on Kafka Connect's REST API server. Similar to the <code>listeners</code> configuration, this field should contain a list of listeners in the following format: <code>protocol://host:port,protocol2://host2:port2</code>. Currently supported protocols are <code>http</code> and <code>https</code>.
+ For example:</p>
+
+ <pre><code class="language-text">admin.listeners=http://localhost:8080,https://localhost:8443</code></pre>
+
+ <p>By default, if <code>admin.listeners</code> is not configured, the admin REST APIs will be available on the regular listeners.</p>
+
+ <p>The following are the currently supported admin REST API endpoints:</p>
+
+ <ul>
+ <li><code>GET /admin/loggers</code> - list the current loggers that have their levels explicitly set and their log levels</li>
+ <li><code>GET /admin/loggers/{name}</code> - get the log level for the specified logger</li>
+ <li><code>PUT /admin/loggers/{name}</code> - set the log level for the specified logger</li>
+ </ul>
+
+ <p>See <a href="https://cwiki.apache.org/confluence/x/-4tTBw">KIP-495</a> for more details about the admin logger REST APIs.</p>
+
+ <p>For the complete specification of the Kafka Connect REST API, see the <a href="/{{version}}/generated/connect_rest.yaml">OpenAPI documentation</a></p>
+
+ <h4><a id="connect_errorreporting" href="#connect_errorreporting">Error Reporting in Connect</a></h4>
+
+ <p>Kafka Connect provides error reporting to handle errors encountered along various stages of processing. By default, any error encountered during conversion or within transformations will cause the connector to fail. Each connector configuration can also enable tolerating such errors by skipping them, optionally writing each error and the details of the failed operation and problematic record (with various levels of detail) to the Connect application log. These mechanisms also capt [...]
+
+ <p>To report errors within a connector's converter, transforms, or within the sink connector itself to the log, set <code>errors.log.enable=true</code> in the connector configuration to log details of each error and problem record's topic, partition, and offset. For additional debugging purposes, set <code>errors.log.include.messages=true</code> to also log the problem record key, value, and headers to the log (note this may log sensitive information).</p>
+
+ <p>To report errors within a connector's converter, transforms, or within the sink connector itself to a dead letter queue topic, set <code>errors.deadletterqueue.topic.name</code>, and optionally <code>errors.deadletterqueue.context.headers.enable=true</code>.</p>
+
+ <p>By default connectors exhibit "fail fast" behavior immediately upon an error or exception. This is equivalent to adding the following configuration properties with their defaults to a connector configuration:</p>
+
+ <pre><code class="language-text"># disable retries on failure
+errors.retry.timeout=0
+
+# do not log the error and their contexts
+errors.log.enable=false
+
+# do not record errors in a dead letter queue topic
+errors.deadletterqueue.topic.name=
+
+# Fail on first error
+errors.tolerance=none</code></pre>
+
+ <p>These and other related connector configuration properties can be changed to provide different behavior. For example, the following configuration properties can be added to a connector configuration to setup error handling with multiple retries, logging to the application logs and the <code>my-connector-errors</code> Kafka topic, and tolerating all errors by reporting them rather than failing the connector task:</p>
+
+ <pre><code class="language-text"># retry for at most 10 minutes times waiting up to 30 seconds between consecutive failures
+errors.retry.timeout=600000
+errors.retry.delay.max.ms=30000
+
+# log error context along with application logs, but do not include configs and messages
+errors.log.enable=true
+errors.log.include.messages=false
+
+# produce error context into the Kafka topic
+errors.deadletterqueue.topic.name=my-connector-errors
+
+# Tolerate all errors.
+errors.tolerance=all</code></pre>
+
+ <h4><a id="connect_exactlyonce" href="#connect_exactlyonce">Exactly-once support</a></h4>
+
+ <p>Kafka Connect is capable of providing exactly-once semantics for sink connectors (as of version 0.11.0) and source connectors (as of version 3.3.0). Please note that <b>support for exactly-once semantics is highly dependent on the type of connector you run.</b> Even if you set all the correct worker properties in the configuration for each node in a cluster, if a connector is not designed to, or cannot take advantage of the capabilities of the Kafka Connect framework, exactly-once [...]
+
+ <h5><a id="connect_exactlyoncesink" href="#connect_exactlyoncesink">Sink connectors</a></h5>
+
+ <p>If a sink connector supports exactly-once semantics, to enable exactly-once at the Connect worker level, you must ensure its consumer group is configured to ignore records in aborted transactions. You can do this by setting the worker property <code>consumer.isolation.level</code> to <code>read_committed</code> or, if running a version of Kafka Connect that supports it, using a <a href="#connectconfigs_connector.client.config.override.policy">connector client config override polic [...]
+
+ <h5><a id="connect_exactlyoncesource" href="#connect_exactlyoncesource">Source connectors</a></h5>
+
+ <p>If a source connector supports exactly-once semantics, you must configure your Connect cluster to enable framework-level support for exactly-once source connectors. Additional ACLs may be necessary if running against a secured Kafka cluster. Note that exactly-once support for source connectors is currently only available in distributed mode; standalone Connect workers cannot provide exactly-once semantics.</p>
+
+ <h6>Worker configuration</h6>
+
+ <p>For new Connect clusters, set the <code>exactly.once.source.support</code> property to <code>enabled</code> in the worker config for each node in the cluster. For existing clusters, two rolling upgrades are necessary. During the first upgrade, the <code>exactly.once.source.support</code> property should be set to <code>preparing</code>, and during the second, it should be set to <code>enabled</code>.</p>
+
+ <h6>ACL requirements</h6>
+
+ <p>With exactly-once source support enabled, or with <code>exactly.once.source.support</code> set to <code>preparing</code>, the principal for each Connect worker will require the following ACLs:</p>
+
+ <table class="data-table">
+ <thead>
+ <tr>
+ <th>Operation</th>
+ <th>Resource Type</th>
+ <th>Resource Name</th>
+ <th>Note</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Write</td>
+ <td>TransactionalId</td>
+ <td><code>connect-cluster-${groupId}</code>, where <code>${groupId}</code> is the <code>group.id</code> of the cluster</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Describe</td>
+ <td>TransactionalId</td>
+ <td><code>connect-cluster-${groupId}</code>, where <code>${groupId}</code> is the <code>group.id</code> of the cluster</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>IdempotentWrite</td>
+ <td>Cluster</td>
+ <td>ID of the Kafka cluster that hosts the worker's config topic</td>
+ <td>The IdempotentWrite ACL has been deprecated as of 2.8 and will only be necessary for Connect clusters running on pre-2.8 Kafka clusters</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>And with exactly-once source enabled (but not if <code>exactly.once.source.support</code> is set to <code>preparing</code>), the principal for each individual connector will require the following ACLs:</p>
+
+ <table class="data-table">
+ <thead>
+ <tr>
+ <th>Operation</th>
+ <th>Resource Type</th>
+ <th>Resource Name</th>
+ <th>Note</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Write</td>
+ <td>TransactionalId</td>
+ <td><code>${groupId}-${connector}-${taskId}</code>, for each task that the connector will create, where <code>${groupId}</code> is the <code>group.id</code> of the Connect cluster, <code>${connector}</code> is the name of the connector, and <code>${taskId}</code> is the ID of the task (starting from zero)</td>
+ <td>A wildcard prefix of <code>${groupId}-${connector}*</code> can be used for convenience if there is no risk of conflict with other transactional IDs or if conflicts are acceptable to the user.</td>
+ </tr>
+ <tr>
+ <td>Describe</td>
+ <td>TransactionalId</td>
+ <td><code>${groupId}-${connector}-${taskId}</code>, for each task that the connector will create, where <code>${groupId}</code> is the <code>group.id</code> of the Connect cluster, <code>${connector}</code> is the name of the connector, and <code>${taskId}</code> is the ID of the task (starting from zero)</td>
+ <td>A wildcard prefix of <code>${groupId}-${connector}*</code> can be used for convenience if there is no risk of conflict with other transactional IDs or if conflicts are acceptable to the user.</td>
+ </tr>
+ <tr>
+ <td>Write</td>
+ <td>Topic</td>
+ <td>Offsets topic used by the connector, which is either the value of the <code>offsets.storage.topic</code> property in the connector’s configuration if provided, or the value of the <code>offsets.storage.topic</code> property in the worker’s configuration if not.</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Read</td>
+ <td>Topic</td>
+ <td>Offsets topic used by the connector, which is either the value of the <code>offsets.storage.topic</code> property in the connector’s configuration if provided, or the value of the <code>offsets.storage.topic</code> property in the worker’s configuration if not.</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Describe</td>
+ <td>Topic</td>
+ <td>Offsets topic used by the connector, which is either the value of the <code>offsets.storage.topic</code> property in the connector’s configuration if provided, or the value of the <code>offsets.storage.topic</code> property in the worker’s configuration if not.</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Create</td>
+ <td>Topic</td>
+ <td>Offsets topic used by the connector, which is either the value of the <code>offsets.storage.topic</code> property in the connector’s configuration if provided, or the value of the <code>offsets.storage.topic</code> property in the worker’s configuration if not.</td>
+ <td>Only necessary if the offsets topic for the connector does not exist yet</td>
+ </tr>
+ <tr>
+ <td>IdempotentWrite</td>
+ <td>Cluster</td>
+ <td>ID of the Kafka cluster that the source connector writes to</td>
+ <td>The IdempotentWrite ACL has been deprecated as of 2.8 and will only be necessary for Connect clusters running on pre-2.8 Kafka clusters</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <h4><a id="connect_plugindiscovery" href="#connect_plugindiscovery">Plugin Discovery</a></h4>
+
+ <p>Plugin discovery is the name for the strategy which the Connect worker uses to find plugin classes and make them accessible to configure and run in connectors. This is controlled by the <a href="#connectconfigs_plugin.discovery">plugin.discovery</a> worker configuration, and has a significant impact on worker startup time. <code>service_load</code> is the fastest strategy, but care should be taken to verify that plugins are compatible before setting this configuration to <code>ser [...]
+
+ <p>Prior to version 3.6, this strategy was not configurable, and behaved like the <code>only_scan</code> mode which is compatible with all plugins. For version 3.6 and later, this mode defaults to <code>hybrid_warn</code> which is also compatible with all plugins, but logs a warning for plugins which are incompatible with <code>service_load</code>. The <code>hybrid_fail</code> strategy stops the worker with an error if a plugin incompatible with <code>service_load</code> is detected, [...]
+
+ <h5><a id="connect_plugindiscovery_compatibility" href="#connect_plugindiscovery_compatibility">Verifying Plugin Compatibility</a></h5>
+
+ <p>To verify if all of your plugins are compatible with <code>service_load</code>, first ensure that you are using version 3.6 or later of Kafka Connect. You can then perform one of the following checks:</p>
+
+ <ul>
+ <li>Start your worker with the default <code>hybrid_warn</code>strategy, and WARN logs enabled for the <code>org.apache.kafka.connect</code> package. At least one WARN log message mentioning the <code>plugin.discovery</code> configuration should be printed. This log message will explicitly say that all plugins are compatible, or list the incompatible plugins.</li>
+ <li>Start your worker in a test environment with <code>hybrid_fail</code>. If all plugins are compatible, startup will succeed. If at least one plugin is not compatible the worker will fail to start up, and all incompatible plugins will be listed in the exception.</li>
+ </ul>
+
+ <p>If the verification step succeeds, then your current set of installed plugins is compatible, and it should be safe to change the <code>plugin.discovery</code> configuration to <code>service_load</code>. If the verification fails, you cannot use <code>service_load</code> strategy and should take note of the list of incompatible plugins. All plugins must be addressed before using the <code>service_load</code> strategy. It is recommended to perform this verification after installing [...]
+
+ <h5><a id="connect_plugindiscovery_migrateartifact" href="#connect_plugindiscovery_migrateartifact">Operators: Artifact Migration</a></h5>
+
+ <p>As an operator of Connect, if you discover incompatible plugins, there are multiple ways to resolve the incompatibility. They are listed below from most to least preferable.</p>
+
+ <ol>
+ <li>Check the latest release from your plugin provider, and if it is compatible, upgrade.</li>
+ <li>Contact your plugin provider and request that they migrate the plugin to be compatible, following the <a href="#connect_plugindiscovery_migratesource">source migration instructions</a>, and then upgrade to the compatible version.</li>
+ <li>Migrate the plugin artifacts yourself using the included migration script.</li>
+ </ol>
+
+ <p>The migration script is located in <code>bin/connect-plugin-path.sh</code> and <code>bin\windows\connect-plugin-path.bat</code> of your Kafka installation. The script can migrate incompatible plugin artifacts already installed on your Connect worker's <code>plugin.path</code> by adding or modifying JAR or resource files. This is not suitable for environments using code-signing, as this can change artifacts such that they will fail signature verification. View the built-in help wit [...]
+
+ <p>To perform a migration, first use the <code>list</code> subcommand to get an overview of the plugins available to the script. You must tell the script where to find plugins, which can be done with the repeatable <code>--worker-config</code>, <code>--plugin-path</code>, and <code>--plugin-location</code> arguments. The script will ignore plugins on the classpath, so any custom plugins on your classpath should be moved to the plugin path in order to be used with this migration scrip [...]
+
+ <p>Once you see that all incompatible plugins are included in the listing, you can proceed to dry-run the migration with <code>sync-manifests --dry-run</code>. This will perform all parts of the migration, except for writing the results of the migration to disk. Note that the <code>sync-manifests</code> command requires all specified paths to be writable, and may alter the contents of the directories. Make a backup of your plugins in the specified paths, or copy them to a writable di [...]
+
+ <p>Ensure that you have a backup of your plugins and the dry-run succeeds before removing the <code>--dry-run</code> flag and actually running the migration. If the migration fails without the <code>--dry-run</code> flag, then the partially migrated artifacts should be discarded. The migration is idempotent, so running it multiple times and on already-migrated plugins is safe. After the script finishes, you should <a href="#connect_plugindiscovery_compatibility">verify the migration [...]
+
+ <h5><a id="connect_plugindiscovery_migratesource" href="#connect_plugindiscovery_migratesource">Developers: Source Migration</a></h5>
+
+ <p>To make plugins compatible with <code>service_load</code>, it is necessary to add <a href="https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html">ServiceLoader</a> manifests to your source code, which should then be packaged in the release artifact. Manifests are resource files in <code>META-INF/services/</code> named after their superclass type, and contain a list of fully-qualified subclass names, one on each line.</p>
+
+ <p>In order for a plugin to be compatible, it must appear as a line in a manifest corresponding to the plugin superclass it extends. If a single plugin implements multiple plugin interfaces, then it should appear in a manifest for each interface it implements. If you have no classes for a certain type of plugin, you do not need to include a manifest file for that type. If you have classes which should not be visible as plugins, they should be marked abstract. The following types are [...]
+
+ <ul>
+ <li><code>org.apache.kafka.connect.sink.SinkConnector</code></li>
+ <li><code>org.apache.kafka.connect.source.SourceConnector</code></li>
+ <li><code>org.apache.kafka.connect.storage.Converter</code></li>
+ <li><code>org.apache.kafka.connect.storage.HeaderConverter</code></li>
+ <li><code>org.apache.kafka.connect.transforms.Transformation</code></li>
+ <li><code>org.apache.kafka.connect.transforms.predicates.Predicate</code></li>
+ <li><code>org.apache.kafka.common.config.provider.ConfigProvider</code></li>
+ <li><code>org.apache.kafka.connect.rest.ConnectRestExtension</code></li>
+ <li><code>org.apache.kafka.connect.connector.policy.ConnectorClientConfigOverridePolicy</code></li>
+ </ul>
+
+ <p>For example, if you only have one connector with the fully-qualified name <code>com.example.MySinkConnector</code>, then only one manifest file must be added to resources in <code>META-INF/services/org.apache.kafka.connect.sink.SinkConnector</code>, and the contents should be similar to the following:</p>
+
+ <pre><code class="language-text"># license header or comment
+com.example.MySinkConnector</code></pre>
+
+ <p>You should then verify that your manifests are correct by using the <a href="#connect_plugindiscovery_compatibility">verification steps</a> with a pre-release artifact. If the verification succeeds, you can then release the plugin normally, and operators can upgrade to the compatible version.</p>
+
+ <h3><a id="connect_development" href="#connect_development">8.3 Connector Development Guide</a></h3>
+
+ <p>This guide describes how developers can write new connectors for Kafka Connect to move data between Kafka and other systems. It briefly reviews a few key concepts and then describes how to create a simple connector.</p>
+
+ <h4><a id="connect_concepts" href="#connect_concepts">Core Concepts and APIs</a></h4>
+
+ <h5><a id="connect_connectorsandtasks" href="#connect_connectorsandtasks">Connectors and Tasks</a></h5>
+
+ <p>To copy data between Kafka and another system, users create a <code>Connector</code> for the system they want to pull data from or push data to. Connectors come in two flavors: <code>SourceConnectors</code> import data from another system (e.g. <code>JDBCSourceConnector</code> would import a relational database into Kafka) and <code>SinkConnectors</code> export data (e.g. <code>HDFSSinkConnector</code> would export the contents of a Kafka topic to an HDFS file).</p>
+
+ <p><code>Connectors</code> do not perform any data copying themselves: their configuration describes the data to be copied, and the <code>Connector</code> is responsible for breaking that job into a set of <code>Tasks</code> that can be distributed to workers. These <code>Tasks</code> also come in two corresponding flavors: <code>SourceTask</code> and <code>SinkTask</code>.</p>
+
+ <p>With an assignment in hand, each <code>Task</code> must copy its subset of the data to or from Kafka. In Kafka Connect, it should always be possible to frame these assignments as a set of input and output streams consisting of records with consistent schemas. Sometimes this mapping is obvious: each file in a set of log files can be considered a stream with each parsed line forming a record using the same schema and offsets stored as byte offsets in the file. In other cases it may [...]
+
+
+ <h5><a id="connect_streamsandrecords" href="#connect_streamsandrecords">Streams and Records</a></h5>
+
+ <p>Each stream should be a sequence of key-value records. Both the keys and values can have complex structure -- many primitive types are provided, but arrays, objects, and nested data structures can be represented as well. The runtime data format does not assume any particular serialization format; this conversion is handled internally by the framework.</p>
+
+ <p>In addition to the key and value, records (both those generated by sources and those delivered to sinks) have associated stream IDs and offsets. These are used by the framework to periodically commit the offsets of data that have been processed so that in the event of failures, processing can resume from the last committed offsets, avoiding unnecessary reprocessing and duplication of events.</p>
+
+ <h5><a id="connect_dynamicconnectors" href="#connect_dynamicconnectors">Dynamic Connectors</a></h5>
+
+ <p>Not all jobs are static, so <code>Connector</code> implementations are also responsible for monitoring the external system for any changes that might require reconfiguration. For example, in the <code>JDBCSourceConnector</code> example, the <code>Connector</code> might assign a set of tables to each <code>Task</code>. When a new table is created, it must discover this so it can assign the new table to one of the <code>Tasks</code> by updating its configuration. When it notices a c [...]
+
+
+ <h4><a id="connect_developing" href="#connect_developing">Developing a Simple Connector</a></h4>
+
+ <p>Developing a connector only requires implementing two interfaces, the <code>Connector</code> and <code>Task</code>. A simple example is included with the source code for Kafka in the <code>file</code> package. This connector is meant for use in standalone mode and has implementations of a <code>SourceConnector</code>/<code>SourceTask</code> to read each line of a file and emit it as a record and a <code>SinkConnector</code>/<code>SinkTask</code> that writes each record to a file.</p>
+
+ <p>The rest of this section will walk through some code to demonstrate the key steps in creating a connector, but developers should also refer to the full example source code as many details are omitted for brevity.</p>
+
+ <h5><a id="connect_connectorexample" href="#connect_connectorexample">Connector Example</a></h5>
+
+ <p>We'll cover the <code>SourceConnector</code> as a simple example. <code>SinkConnector</code> implementations are very similar. Pick a package and class name, these examples will use the <code>FileStreamSourceConnector</code> but substitute your own class name where appropriate. In order to <a href="#connect_plugindiscovery">make the plugin discoverable at runtime</a>, add a ServiceLoader manifest to your resources in <code>META-INF/services/org.apache.kafka.connect.source.SourceCo [...]
+ <pre><code class="language-resource">com.example.FileStreamSourceConnector</code></pre>
+
+ <p>Create a class that inherits from <code>SourceConnector</code> and add a field that will store the configuration information to be propagated to the task(s) (the topic to send data to, and optionally - the filename to read from and the maximum batch size):</p>
+
+ <pre class="line-numbers"><code class="language-java">package com.example;
+
+public class FileStreamSourceConnector extends SourceConnector {
+ private Map<String, String> props;</code></pre>
+
+ <p>The easiest method to fill in is <code>taskClass()</code>, which defines the class that should be instantiated in worker processes to actually read the data:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public Class<? extends Task> taskClass() {
+ return FileStreamSourceTask.class;
+}</code></pre>
+
+ <p>We will define the <code>FileStreamSourceTask</code> class below. Next, we add some standard lifecycle methods, <code>start()</code> and <code>stop()</code>:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public void start(Map<String, String> props) {
+ // Initialization logic and setting up of resources can take place in this method.
+ // This connector doesn't need to do any of that, but we do log a helpful message to the user.
+
+ this.props = props;
+ AbstractConfig config = new AbstractConfig(CONFIG_DEF, props);
+ String filename = config.getString(FILE_CONFIG);
+ filename = (filename == null || filename.isEmpty()) ? "standard input" : config.getString(FILE_CONFIG);
+ log.info("Starting file source connector reading from {}", filename);
+}
+
+@Override
+public void stop() {
+ // Nothing to do since no background monitoring is required.
+}</code></pre>
+
+ <p>Finally, the real core of the implementation is in <code>taskConfigs()</code>. In this case we are only
+ handling a single file, so even though we may be permitted to generate more tasks as per the
+ <code>maxTasks</code> argument, we return a list with only one entry:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public List<Map<String, String>> taskConfigs(int maxTasks) {
+ // Note that the task configs could contain configs additional to or different from the connector configs if needed. For instance,
+ // if different tasks have different responsibilities, or if different tasks are meant to process different subsets of the source data stream).
+ ArrayList<Map<String, String>> configs = new ArrayList<>();
+ // Only one input stream makes sense.
+ configs.add(props);
+ return configs;
+}</code></pre>
+
+ <p>Even with multiple tasks, this method implementation is usually pretty simple. It just has to determine the number of input tasks, which may require contacting the remote service it is pulling data from, and then divvy them up. Because some patterns for splitting work among tasks are so common, some utilities are provided in <code>ConnectorUtils</code> to simplify these cases.</p>
+
+ <p>Note that this simple example does not include dynamic input. See the discussion in the next section for how to trigger updates to task configs.</p>
+
+ <h5><a id="connect_taskexample" href="#connect_taskexample">Task Example - Source Task</a></h5>
+
+ <p>Next we'll describe the implementation of the corresponding <code>SourceTask</code>. The implementation is short, but too long to cover completely in this guide. We'll use pseudo-code to describe most of the implementation, but you can refer to the source code for the full example.</p>
+
+ <p>Just as with the connector, we need to create a class inheriting from the appropriate base <code>Task</code> class. It also has some standard lifecycle methods:</p>
+
+
+ <pre class="line-numbers"><code class="language-java">public class FileStreamSourceTask extends SourceTask {
+ private String filename;
+ private InputStream stream;
+ private String topic;
+ private int batchSize;
+
+ @Override
+ public void start(Map<String, String> props) {
+ filename = props.get(FileStreamSourceConnector.FILE_CONFIG);
+ stream = openOrThrowError(filename);
+ topic = props.get(FileStreamSourceConnector.TOPIC_CONFIG);
+ batchSize = props.get(FileStreamSourceConnector.TASK_BATCH_SIZE_CONFIG);
+ }
+
+ @Override
+ public synchronized void stop() {
+ stream.close();
+ }
+}</code></pre>
+
+ <p>These are slightly simplified versions, but show that these methods should be relatively simple and the only work they should perform is allocating or freeing resources. There are two points to note about this implementation. First, the <code>start()</code> method does not yet handle resuming from a previous offset, which will be addressed in a later section. Second, the <code>stop()</code> method is synchronized. This will be necessary because <code>SourceTasks</code> are given a [...]
+
+ <p>Next, we implement the main functionality of the task, the <code>poll()</code> method which gets events from the input system and returns a <code>List<SourceRecord></code>:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public List<SourceRecord> poll() throws InterruptedException {
+ try {
+ ArrayList<SourceRecord> records = new ArrayList<>();
+ while (streamValid(stream) && records.isEmpty()) {
+ LineAndOffset line = readToNextLine(stream);
+ if (line != null) {
+ Map<String, Object> sourcePartition = Collections.singletonMap("filename", filename);
+ Map<String, Object> sourceOffset = Collections.singletonMap("position", streamOffset);
+ records.add(new SourceRecord(sourcePartition, sourceOffset, topic, Schema.STRING_SCHEMA, line));
+ if (records.size() >= batchSize) {
+ return records;
+ }
+ } else {
+ Thread.sleep(1);
+ }
+ }
+ return records;
+ } catch (IOException e) {
+ // Underlying stream was killed, probably as a result of calling stop. Allow to return
+ // null, and driving thread will handle any shutdown if necessary.
+ }
+ return null;
+}</code></pre>
+
+ <p>Again, we've omitted some details, but we can see the important steps: the <code>poll()</code> method is going to be called repeatedly, and for each call it will loop trying to read records from the file. For each line it reads, it also tracks the file offset. It uses this information to create an output <code>SourceRecord</code> with four pieces of information: the source partition (there is only one, the single file being read), source offset (byte offset in the file), output to [...]
+
+ <p>Note that this implementation uses the normal Java <code>InputStream</code> interface and may sleep if data is not available. This is acceptable because Kafka Connect provides each task with a dedicated thread. While task implementations have to conform to the basic <code>poll()</code> interface, they have a lot of flexibility in how they are implemented. In this case, an NIO-based implementation would be more efficient, but this simple approach works, is quick to implement, and i [...]
+
+ <p>Although not used in the example, <code>SourceTask</code> also provides two APIs to commit offsets in the source system: <code>commit</code> and <code>commitRecord</code>. The APIs are provided for source systems which have an acknowledgement mechanism for messages. Overriding these methods allows the source connector to acknowledge messages in the source system, either in bulk or individually, once they have been written to Kafka.
+ The <code>commit</code> API stores the offsets in the source system, up to the offsets that have been returned by <code>poll</code>. The implementation of this API should block until the commit is complete. The <code>commitRecord</code> API saves the offset in the source system for each <code>SourceRecord</code> after it is written to Kafka. As Kafka Connect will record offsets automatically, <code>SourceTask</code>s are not required to implement them. In cases where a connector [...]
+
+ <h5><a id="connect_sinktasks" href="#connect_sinktasks">Sink Tasks</a></h5>
+
+ <p>The previous section described how to implement a simple <code>SourceTask</code>. Unlike <code>SourceConnector</code> and <code>SinkConnector</code>, <code>SourceTask</code> and <code>SinkTask</code> have very different interfaces because <code>SourceTask</code> uses a pull interface and <code>SinkTask</code> uses a push interface. Both share the common lifecycle methods, but the <code>SinkTask</code> interface is quite different:</p>
+
+ <pre class="line-numbers"><code class="language-java">public abstract class SinkTask implements Task {
+ public void initialize(SinkTaskContext context) {
+ this.context = context;
+ }
+
+ public abstract void put(Collection<SinkRecord> records);
+
+ public void flush(Map<TopicPartition, OffsetAndMetadata> currentOffsets) {
+ }
+}</code></pre>
+
+ <p>The <code>SinkTask</code> documentation contains full details, but this interface is nearly as simple as the <code>SourceTask</code>. The <code>put()</code> method should contain most of the implementation, accepting sets of <code>SinkRecords</code>, performing any required translation, and storing them in the destination system. This method does not need to ensure the data has been fully written to the destination system before returning. In fact, in many cases internal buffering [...]
+
+ <p>The <code>flush()</code> method is used during the offset commit process, which allows tasks to recover from failures and resume from a safe point such that no events will be missed. The method should push any outstanding data to the destination system and then block until the write has been acknowledged. The <code>offsets</code> parameter can often be ignored, but is useful in some cases where implementations want to store offset information in the destination store to provide ex [...]
+ delivery. For example, an HDFS connector could do this and use atomic move operations to make sure the <code>flush()</code> operation atomically commits the data and offsets to a final location in HDFS.</p>
+
+ <h5><a id="connect_errantrecordreporter" href="connect_errantrecordreporter">Errant Record Reporter</a></h5>
+
+ <p>When <a href="#connect_errorreporting">error reporting</a> is enabled for a connector, the connector can use an <code>ErrantRecordReporter</code> to report problems with individual records sent to a sink connector. The following example shows how a connector's <code>SinkTask</code> subclass might obtain and use the <code>ErrantRecordReporter</code>, safely handling a null reporter when the DLQ is not enabled or when the connector is installed in an older Connect runtime that doesn [...]
+
+ <pre class="line-numbers"><code class="language-java">private ErrantRecordReporter reporter;
+
+@Override
+public void start(Map<String, String> props) {
+ ...
+ try {
+ reporter = context.errantRecordReporter(); // may be null if DLQ not enabled
+ } catch (NoSuchMethodException | NoClassDefFoundError e) {
+ // Will occur in Connect runtimes earlier than 2.6
+ reporter = null;
+ }
+}
+
+@Override
+public void put(Collection<SinkRecord> records) {
+ for (SinkRecord record: records) {
+ try {
+ // attempt to process and send record to data sink
+ process(record);
+ } catch(Exception e) {
+ if (reporter != null) {
+ // Send errant record to error reporter
+ reporter.report(record, e);
+ } else {
+ // There's no error reporter, so fail
+ throw new ConnectException("Failed on record", e);
+ }
+ }
+ }
+}</code></pre>
+
+ <h5><a id="connect_resuming" href="#connect_resuming">Resuming from Previous Offsets</a></h5>
+
+ <p>The <code>SourceTask</code> implementation included a stream ID (the input filename) and offset (position in the file) with each record. The framework uses this to commit offsets periodically so that in the case of a failure, the task can recover and minimize the number of events that are reprocessed and possibly duplicated (or to resume from the most recent offset if Kafka Connect was stopped gracefully, e.g. in standalone mode or due to a job reconfiguration). This commit proces [...]
+
+ <p>To correctly resume upon startup, the task can use the <code>SourceContext</code> passed into its <code>initialize()</code> method to access the offset data. In <code>initialize()</code>, we would add a bit more code to read the offset (if it exists) and seek to that position:</p>
+
+ <pre class="line-numbers"><code class="language-java">stream = new FileInputStream(filename);
+Map<String, Object> offset = context.offsetStorageReader().offset(Collections.singletonMap(FILENAME_FIELD, filename));
+if (offset != null) {
+ Long lastRecordedOffset = (Long) offset.get("position");
+ if (lastRecordedOffset != null)
+ seekToOffset(stream, lastRecordedOffset);
+}</code></pre>
+
+ <p>Of course, you might need to read many keys for each of the input streams. The <code>OffsetStorageReader</code> interface also allows you to issue bulk reads to efficiently load all offsets, then apply them by seeking each input stream to the appropriate position.</p>
+
+ <h5><a id="connect_exactlyoncesourceconnectors" href="#connect_exactlyoncesourceconnectors">Exactly-once source connectors</a></h5>
+
+ <h6>Supporting exactly-once</h6>
+
+ <p>With the passing of <a href="https://cwiki.apache.org/confluence/x/Vg0rCQ">KIP-618</a>, Kafka Connect supports exactly-once source connectors as of version 3.3.0. In order for a source connector to take advantage of this support, it must be able to provide meaningful source offsets for each record that it emits, and resume consumption from the external system at the exact position corresponding to any of those offsets without dropping or duplicating messages.</p>
+
+ <h6>Defining transaction boundaries</h6>
+
+ <p>By default, the Kafka Connect framework will create and commit a new Kafka transaction for each batch of records that a source task returns from its <code>poll</code> method. However, connectors can also define their own transaction boundaries, which can be enabled by users by setting the <code>transaction.boundary</code> property to <code>connector</code> in the config for the connector.</p>
+
+ <p>If enabled, the connector's tasks will have access to a <code>TransactionContext</code> from their <code>SourceTaskContext</code>, which they can use to control when transactions are aborted and committed.</p>
+
+ <p>For example, to commit a transaction at least every ten records:</p>
+
+ <pre class="line-numbers"><code class="language-java">private int recordsSent;
+
+@Override
+public void start(Map<String, String> props) {
+ this.recordsSent = 0;
+}
+
+@Override
+public List<SourceRecord> poll() {
+ List<SourceRecord> records = fetchRecords();
+ boolean shouldCommit = false;
+ for (SourceRecord record : records) {
+ if (++this.recordsSent >= 10) {
+ shouldCommit = true;
+ }
+ }
+ if (shouldCommit) {
+ this.recordsSent = 0;
+ this.context.transactionContext().commitTransaction();
+ }
+ return records;
+}</code></pre>
+
+ <p>Or to commit a transaction for exactly every tenth record:</p>
+
+ <pre class="line-numbers"><code class="language-java">private int recordsSent;
+
+@Override
+public void start(Map<String, String> props) {
+ this.recordsSent = 0;
+}
+
+@Override
+public List<SourceRecord> poll() {
+ List<SourceRecord> records = fetchRecords();
+ for (SourceRecord record : records) {
+ if (++this.recordsSent % 10 == 0) {
+ this.context.transactionContext().commitTransaction(record);
+ }
+ }
+ return records;
+}</code></pre>
+
+ <p>Most connectors do not need to define their own transaction boundaries. However, it may be useful if files or objects in the source system are broken up into multiple source records, but should be delivered atomically. Additionally, it may be useful if it is impossible to give each source record a unique source offset, if every record with a given offset is delivered within a single transaction.</p>
+
+ <p>Note that if the user has not enabled connector-defined transaction boundaries in the connector configuration, the <code>TransactionContext</code> returned by <code>context.transactionContext()</code> will be <code>null</code>.</p>
+
+ <h6>Validation APIs</h6>
+
+ <p>A few additional preflight validation APIs can be implemented by source connector developers.</p>
+
+ <p>Some users may require exactly-once semantics from a connector. In this case, they may set the <code>exactly.once.support</code> property to <code>required</code> in the configuration for the connector. When this happens, the Kafka Connect framework will ask the connector whether it can provide exactly-once semantics with the specified configuration. This is done by invoking the <code>exactlyOnceSupport</code> method on the connector.</p>
+
+ <p>If a connector doesn't support exactly-once semantics, it should still implement this method to let users know for certain that it cannot provide exactly-once semantics:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public ExactlyOnceSupport exactlyOnceSupport(Map<String, String> props) {
+ // This connector cannot provide exactly-once semantics under any conditions
+ return ExactlyOnceSupport.UNSUPPORTED;
+}
+</code></pre>
+
+ <p>Otherwise, a connector should examine the configuration, and return <code>ExactlyOnceSupport.SUPPORTED</code> if it can provide exactly-once semantics:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public ExactlyOnceSupport exactlyOnceSupport(Map<String, String> props) {
+ // This connector can always provide exactly-once semantics
+ return ExactlyOnceSupport.SUPPORTED;
+}</code></pre>
+
+ <p>Additionally, if the user has configured the connector to define its own transaction boundaries, the Kafka Connect framework will ask the connector whether it can define its own transaction boundaries with the specified configuration, using the <code>canDefineTransactionBoundaries</code> method:</p>
+
+ <pre class="line-numbers"><code class="language-java">@Override
+public ConnectorTransactionBoundaries canDefineTransactionBoundaries(Map<String, String> props) {
+ // This connector can always define its own transaction boundaries
+ return ConnectorTransactionBoundaries.SUPPORTED;
+}</code></pre>
+
+ <p>This method should only be implemented for connectors that can define their own transaction boundaries in some cases. If a connector is never able to define its own transaction boundaries, it does not need to implement this method.</p>
+
+ <h4><a id="connect_dynamicio" href="#connect_dynamicio">Dynamic Input/Output Streams</a></h4>
+
+ <p>Kafka Connect is intended to define bulk data copying jobs, such as copying an entire database rather than creating many jobs to copy each table individually. One consequence of this design is that the set of input or output streams for a connector can vary over time.</p>
+
+ <p>Source connectors need to monitor the source system for changes, e.g. table additions/deletions in a database. When they pick up changes, they should notify the framework via the <code>ConnectorContext</code> object that reconfiguration is necessary. For example, in a <code>SourceConnector</code>:</p>
+
+ <pre class="line-numbers"><code class="language-java">if (inputsChanged())
+ this.context.requestTaskReconfiguration();</code></pre>
+
+ <p>The framework will promptly request new configuration information and update the tasks, allowing them to gracefully commit their progress before reconfiguring them. Note that in the <code>SourceConnector</code> this monitoring is currently left up to the connector implementation. If an extra thread is required to perform this monitoring, the connector must allocate it itself.</p>
+
+ <p>Ideally this code for monitoring changes would be isolated to the <code>Connector</code> and tasks would not need to worry about them. However, changes can also affect tasks, most commonly when one of their input streams is destroyed in the input system, e.g. if a table is dropped from a database. If the <code>Task</code> encounters the issue before the <code>Connector</code>, which will be common if the <code>Connector</code> needs to poll for changes, the <code>Task</code> will [...]
+
+ <p><code>SinkConnectors</code> usually only have to handle the addition of streams, which may translate to new entries in their outputs (e.g., a new database table). The framework manages any changes to the Kafka input, such as when the set of input topics changes because of a regex subscription. <code>SinkTasks</code> should expect new input streams, which may require creating new resources in the downstream system, such as a new table in a database. The trickiest situation to handl [...]
+
+ <h4><a id="connect_configs" href="#connect_configs">Configuration Validation</a></h4>
+
+ <p>Kafka Connect allows you to validate connector configurations before submitting a connector to be executed and can provide feedback about errors and recommended values. To take advantage of this, connector developers need to provide an implementation of <code>config()</code> to expose the configuration definition to the framework.</p>
+
+ <p>The following code in <code>FileStreamSourceConnector</code> defines the configuration and exposes it to the framework.</p>
+
+ <pre class="line-numbers"><code class="language-java">static final ConfigDef CONFIG_DEF = new ConfigDef()
+ .define(FILE_CONFIG, Type.STRING, null, Importance.HIGH, "Source filename. If not specified, the standard input will be used")
+ .define(TOPIC_CONFIG, Type.STRING, ConfigDef.NO_DEFAULT_VALUE, new ConfigDef.NonEmptyString(), Importance.HIGH, "The topic to publish data to")
+ .define(TASK_BATCH_SIZE_CONFIG, Type.INT, DEFAULT_TASK_BATCH_SIZE, Importance.LOW,
+ "The maximum number of records the source task can read from the file each time it is polled");
+
+public ConfigDef config() {
+ return CONFIG_DEF;
+}</code></pre>
+
+ <p><code>ConfigDef</code> class is used for specifying the set of expected configurations. For each configuration, you can specify the name, the type, the default value, the documentation, the group information, the order in the group, the width of the configuration value and the name suitable for display in the UI. Plus, you can provide special validation logic used for single configuration validation by overriding the <code>Validator</code> class. Moreover, as there may be dependen [...]
+
+ <p>Also, the <code>validate()</code> method in <code>Connector</code> provides a default validation implementation which returns a list of allowed configurations together with configuration errors and recommended values for each configuration. However, it does not use the recommended values for configuration validation. You may provide an override of the default implementation for customized configuration validation, which may use the recommended values.</p>
+
+ <h4><a id="connect_schemas" href="#connect_schemas">Working with Schemas</a></h4>
+
+ <p>The FileStream connectors are good examples because they are simple, but they also have trivially structured data -- each line is just a string. Almost all practical connectors will need schemas with more complex data formats.</p>
+
+ <p>To create more complex data, you'll need to work with the Kafka Connect <code>data</code> API. Most structured records will need to interact with two classes in addition to primitive types: <code>Schema</code> and <code>Struct</code>.</p>
+
+ <p>The API documentation provides a complete reference, but here is a simple example creating a <code>Schema</code> and <code>Struct</code>:</p>
+
+ <pre class="line-numbers"><code class="language-java">Schema schema = SchemaBuilder.struct().name(NAME)
+ .field("name", Schema.STRING_SCHEMA)
+ .field("age", Schema.INT_SCHEMA)
+ .field("admin", SchemaBuilder.bool().defaultValue(false).build())
+ .build();
+
+Struct struct = new Struct(schema)
+ .put("name", "Barbara Liskov")
+ .put("age", 75);</code></pre>
+
+ <p>If you are implementing a source connector, you'll need to decide when and how to create schemas. Where possible, you should avoid recomputing them as much as possible. For example, if your connector is guaranteed to have a fixed schema, create it statically and reuse a single instance.</p>
+
+ <p>However, many connectors will have dynamic schemas. One simple example of this is a database connector. Considering even just a single table, the schema will not be predefined for the entire connector (as it varies from table to table). But it also may not be fixed for a single table over the lifetime of the connector since the user may execute an <code>ALTER TABLE</code> command. The connector must be able to detect these changes and react appropriately.</p>
+
+ <p>Sink connectors are usually simpler because they are consuming data and therefore do not need to create schemas. However, they should take just as much care to validate that the schemas they receive have the expected format. When the schema does not match -- usually indicating the upstream producer is generating invalid data that cannot be correctly translated to the destination system -- sink connectors should throw an exception to indicate this error to the system.</p>
+
+ <h3><a id="connect_administration" href="#connect_administration">8.4 Administration</a></h3>
+
+ <p>
+ Kafka Connect's <a href="#connect_rest">REST layer</a> provides a set of APIs to enable administration of the cluster. This includes APIs to view the configuration of connectors and the status of their tasks, as well as to alter their current behavior (e.g. changing configuration and restarting tasks).
+ </p>
+
+ <p>
+ When a connector is first submitted to the cluster, a rebalance is triggered between the Connect workers in order to distribute the load that consists of the tasks of the new connector.
+ This same rebalancing procedure is also used when connectors increase or decrease the number of tasks they require, when a connector's configuration is changed, or when a
+ worker is added or removed from the group as part of an intentional upgrade of the Connect cluster or due to a failure.
+ </p>
+
+ <p>
+ In versions prior to 2.3.0, the Connect workers would rebalance the full set of connectors and their tasks in the cluster as a simple way to make sure that each worker has approximately the same amount of work.
+ This behavior can be still enabled by setting <code>connect.protocol=eager</code>.
+ </p>
+
+ <p>
+ Starting with 2.3.0, Kafka Connect is using by default a protocol that performs
+ <a href="https://cwiki.apache.org/confluence/x/Y4MCBg">incremental cooperative rebalancing</a>
+ that incrementally balances the connectors and tasks across the Connect workers, affecting only tasks that are new, to be removed, or need to move from one worker to another.
+ Other tasks are not stopped and restarted during the rebalance, as they would have been with the old protocol.
+ </p>
+
+ <p>
+ If a Connect worker leaves the group, intentionally or due to a failure, Connect waits for <code>scheduled.rebalance.max.delay.ms</code> before triggering a rebalance.
+ This delay defaults to five minutes (<code>300000ms</code>) to tolerate failures or upgrades of workers without immediately redistributing the load of a departing worker.
+ If this worker returns within the configured delay, it gets its previously assigned tasks in full.
+ However, this means that the tasks will remain unassigned until the time specified by <code>scheduled.rebalance.max.delay.ms</code> elapses.
+ If a worker does not return within that time limit, Connect will reassign those tasks among the remaining workers in the Connect cluster.
+ </p>
+
+ <p>
+ The new Connect protocol is enabled when all the workers that form the Connect cluster are configured with <code>connect.protocol=compatible</code>, which is also the default value when this property is missing.
+ Therefore, upgrading to the new Connect protocol happens automatically when all the workers upgrade to 2.3.0.
+ A rolling upgrade of the Connect cluster will activate incremental cooperative rebalancing when the last worker joins on version 2.3.0.
+ </p>
+
+ <p>
+ You can use the REST API to view the current status of a connector and its tasks, including the ID of the worker to which each was assigned. For example, the <code>GET /connectors/file-source/status</code> request shows the status of a connector named <code>file-source</code>:
+ </p>
+
+ <pre class="line-numbers"><code class="language-json">{
+ "name": "file-source",
+ "connector": {
+ "state": "RUNNING",
+ "worker_id": "192.168.1.208:8083"
+ },
+ "tasks": [
+ {
+ "id": 0,
+ "state": "RUNNING",
+ "worker_id": "192.168.1.209:8083"
+ }
+ ]
+}</code></pre>
+
+ <p>
+ Connectors and their tasks publish status updates to a shared topic (configured with <code>status.storage.topic</code>) which all workers in the cluster monitor. Because the workers consume this topic asynchronously, there is typically a (short) delay before a state change is visible through the status API. The following states are possible for a connector or one of its tasks:
+ </p>
+
+ <ul>
+ <li><b>UNASSIGNED:</b> The connector/task has not yet been assigned to a worker.</li>
+ <li><b>RUNNING:</b> The connector/task is running.</li>
+ <li><b>PAUSED:</b> The connector/task has been administratively paused.</li>
+ <li><b>STOPPED:</b> The connector has been stopped. Note that this state is not applicable to tasks because the tasks for a stopped connector are shut down and won't be visible in the status API.</li>
+ <li><b>FAILED:</b> The connector/task has failed (usually by raising an exception, which is reported in the status output).</li>
+ <li><b>RESTARTING:</b> The connector/task is either actively restarting or is expected to restart soon</li>
+ </ul>
+
+ <p>
+ In most cases, connector and task states will match, though they may be different for short periods of time when changes are occurring or if tasks have failed. For example, when a connector is first started, there may be a noticeable delay before the connector and its tasks have all transitioned to the RUNNING state. States will also diverge when tasks fail since Connect does not automatically restart failed tasks. To restart a connector/task manually, you can use the restart APIs li [...]
+ </p>
+
+ <p>
+ Starting with 2.5.0, Kafka Connect uses the <code>status.storage.topic</code> to also store information related to the topics that each connector is using. Connect Workers use these per-connector topic status updates to respond to requests to the REST endpoint <code>GET /connectors/{name}/topics</code> by returning the set of topic names that a connector is using. A request to the REST endpoint <code>PUT /connectors/{name}/topics/reset</code> resets the set of active topics for a con [...]
+ </p>
+
+ <p>
+ It's sometimes useful to temporarily stop the message processing of a connector. For example, if the remote system is undergoing maintenance, it would be preferable for source connectors to stop polling it for new data instead of filling logs with exception spam. For this use case, Connect offers a pause/resume API. While a source connector is paused, Connect will stop polling it for additional records. While a sink connector is paused, Connect will stop pushing new messages to it. T [...]
+ </p>
+
+ <p>
+ In 3.5.0, Connect introduced a stop API that completely shuts down the tasks for a connector and deallocates any resources claimed by them. This is different from pausing a connector where tasks are left idling and any resources claimed by them are left allocated (which allows the connector to begin processing data quickly once it is resumed). Stopping a connector is more efficient from a resource usage standpoint than pausing it, but can cause it to take longer to begin processing d [...]
+ </p>
+</script>
+
+<div class="p-connect"></div>
diff --git a/41/design.html b/41/design.html
new file mode 100644
index 000000000..c58ead07c
--- /dev/null
+++ b/41/design.html
@@ -0,0 +1,764 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<script id="design-template" type="text/x-handlebars-template">
+ <h3 class="anchor-heading"><a id="majordesignelements" class="anchor-link"></a><a href="#majordesignelements">4.1 Motivation</a></h3>
+ <p>
+ We designed Kafka to be able to act as a unified platform for handling all the real-time data feeds <a href="#introduction">a large company might have</a>. To do this we had to think through a fairly broad set of use cases.
+ <p>
+ It would have to have high-throughput to support high volume event streams such as real-time log aggregation.
+ <p>
+ It would need to deal gracefully with large data backlogs to be able to support periodic data loads from offline systems.
+ <p>
+ It also meant the system would have to handle low-latency delivery to handle more traditional messaging use-cases.
+ <p>
+ We wanted to support partitioned, distributed, real-time processing of these feeds to create new, derived feeds. This motivated our partitioning and consumer model.
+ <p>
+ Finally in cases where the stream is fed into other data systems for serving, we knew the system would have to be able to guarantee fault-tolerance in the presence of machine failures.
+ <p>
+ Supporting these uses led us to a design with a number of unique elements, more akin to a database log than a traditional messaging system. We will outline some elements of the design in the following sections.
+
+ <h3 class="anchor-heading"><a id="persistence" class="anchor-link"></a><a href="#persistence">4.2 Persistence</a></h3>
+ <h4><a id="design_filesystem" href="#design_filesystem">Don't fear the filesystem!</a></h4>
+ <p>
+ Kafka relies heavily on the filesystem for storing and caching messages. There is a general perception that "disks are slow" which makes people skeptical that a persistent structure can offer competitive performance.
+ In fact disks are both much slower and much faster than people expect depending on how they are used; and a properly designed disk structure can often be as fast as the network.
+ <p>
+ The key fact about disk performance is that the throughput of hard drives has been diverging from the latency of a disk seek for the last decade. As a result the performance of linear writes on a <a href="https://en.wikipedia.org/wiki/Non-RAID_drive_architectures">JBOD</a>
+ configuration with six 7200rpm SATA RAID-5 array is about 600MB/sec but the performance of random writes is only about 100k/sec—a difference of over 6000X. These linear reads and writes are the most
+ predictable of all usage patterns, and are heavily optimized by the operating system. A modern operating system provides read-ahead and write-behind techniques that prefetch data in large block multiples and
+ group smaller logical writes into large physical writes. A further discussion of this issue can be found in this <a href="https://queue.acm.org/detail.cfm?id=1563874">ACM Queue article</a>; they actually find that
+ <a href="https://deliveryimages.acm.org/10.1145/1570000/1563874/jacobs3.jpg">sequential disk access can in some cases be faster than random memory access!</a>
+ <p>
+ To compensate for this performance divergence, modern operating systems have become increasingly aggressive in their use of main memory for disk caching. A modern OS will happily divert <i>all</i> free memory to
+ disk caching with little performance penalty when the memory is reclaimed. All disk reads and writes will go through this unified cache. This feature cannot easily be turned off without using direct I/O, so even
+ if a process maintains an in-process cache of the data, this data will likely be duplicated in OS pagecache, effectively storing everything twice.
+ <p>
+ Furthermore, we are building on top of the JVM, and anyone who has spent any time with Java memory usage knows two things:
+ <ol>
+ <li>The memory overhead of objects is very high, often doubling the size of the data stored (or worse).</li>
+ <li>Java garbage collection becomes increasingly fiddly and slow as the in-heap data increases.</li>
+ </ol>
+ <p>
+ As a result of these factors using the filesystem and relying on pagecache is superior to maintaining an in-memory cache or other structure—we at least double the available cache by having automatic access
+ to all free memory, and likely double again by storing a compact byte structure rather than individual objects. Doing so will result in a cache of up to 28-30GB on a 32GB machine without GC penalties.
+ Furthermore, this cache will stay warm even if the service is restarted, whereas the in-process cache will need to be rebuilt in memory (which for a 10GB cache may take 10 minutes) or else it will need to start
+ with a completely cold cache (which likely means terrible initial performance). This also greatly simplifies the code as all logic for maintaining coherency between the cache and filesystem is now in the OS,
+ which tends to do so more efficiently and more correctly than one-off in-process attempts. If your disk usage favors linear reads then read-ahead is effectively pre-populating this cache with useful data on each
+ disk read.
+ <p>
+ This suggests a design which is very simple: rather than maintain as much as possible in-memory and flush it all out to the filesystem in a panic when we run out of space, we invert that. All data is immediately
+ written to a persistent log on the filesystem without necessarily flushing to disk. In effect this just means that it is transferred into the kernel's pagecache.
+ <p>
+ This style of pagecache-centric design is described in an <a href="https://varnish-cache.org/wiki/ArchitectNotes">article</a> on the design of Varnish here (along with a healthy dose of arrogance).
+
+ <h4 class="anchor-heading"><a id="design_constanttime" class="anchor-link"></a><a href="#design_constanttime">Constant Time Suffices</a></h4>
+ <p>
+ The persistent data structure used in messaging systems are often a per-consumer queue with an associated BTree or other general-purpose random access data structures to maintain metadata about messages.
+ BTrees are the most versatile data structure available, and make it possible to support a wide variety of transactional and non-transactional semantics in the messaging system.
+ They do come with a fairly high cost, though: Btree operations are O(log N). Normally O(log N) is considered essentially equivalent to constant time, but this is not true for disk operations.
+ Disk seeks come at 10 ms a pop, and each disk can do only one seek at a time so parallelism is limited. Hence even a handful of disk seeks leads to very high overhead.
+ Since storage systems mix very fast cached operations with very slow physical disk operations, the observed performance of tree structures is often superlinear as data increases with fixed cache--i.e. doubling
+ your data makes things much worse than twice as slow.
+ <p>
+ Intuitively a persistent queue could be built on simple reads and appends to files as is commonly the case with logging solutions. This structure has the advantage that all operations are O(1) and reads do not
+ block writes or each other. This has obvious performance advantages since the performance is completely decoupled from the data size—one server can now take full advantage of a number of cheap,
+ low-rotational speed 1+TB SATA drives. Though they have poor seek performance, these drives have acceptable performance for large reads and writes and come at 1/3 the price and 3x the capacity.
+ <p>
+ Having access to virtually unlimited disk space without any performance penalty means that we can provide some features not usually found in a messaging system. For example, in Kafka, instead of attempting to
+ delete messages as soon as they are consumed, we can retain messages for a relatively long period (say a week). This leads to a great deal of flexibility for consumers, as we will describe.
+
+ <h3 class="anchor-heading"><a id="maximizingefficiency" class="anchor-link"></a><a href="#maximizingefficiency">4.3 Efficiency</a></h3>
+ <p>
+ We have put significant effort into efficiency. One of our primary use cases is handling web activity data, which is very high volume: each page view may generate dozens of writes. Furthermore, we assume each
+ message published is read by at least one consumer (often many), hence we strive to make consumption as cheap as possible.
+ <p>
+ We have also found, from experience building and running a number of similar systems, that efficiency is a key to effective multi-tenant operations. If the downstream infrastructure service can easily become a
+ bottleneck due to a small bump in usage by the application, such small changes will often create problems. By being very fast we help ensure that the application will tip-over under load before the infrastructure.
+ This is particularly important when trying to run a centralized service that supports dozens or hundreds of applications on a centralized cluster as changes in usage patterns are a near-daily occurrence.
+ <p>
+ We discussed disk efficiency in the previous section. Once poor disk access patterns have been eliminated, there are two common causes of inefficiency in this type of system: too many small I/O operations, and
+ excessive byte copying.
+ <p>
+ The small I/O problem happens both between the client and the server and in the server's own persistent operations.
+ <p>
+ To avoid this, our protocol is built around a "message set" abstraction that naturally groups messages together. This allows network requests to group messages together and amortize the overhead of the network
+ roundtrip rather than sending a single message at a time. The server in turn appends chunks of messages to its log in one go, and the consumer fetches large linear chunks at a time.
+ <p>
+ This simple optimization produces orders of magnitude speed up. Batching leads to larger network packets, larger sequential disk operations, contiguous memory blocks, and so on, all of which allows Kafka to turn
+ a bursty stream of random message writes into linear writes that flow to the consumers.
+ <p>
+ The other inefficiency is in byte copying. At low message rates this is not an issue, but under load the impact is significant. To avoid this we employ a standardized binary message format that is shared by the
+ producer, the broker, and the consumer (so data chunks can be transferred without modification between them).
+ <p>
+ The message log maintained by the broker is itself just a directory of files, each populated by a sequence of message sets that have been written to disk in the same format used by the producer and consumer.
+ Maintaining this common format allows optimization of the most important operation: network transfer of persistent log chunks. Modern unix operating systems offer a highly optimized code path for transferring data
+ out of pagecache to a socket; in Linux this is done with the <a href="https://man7.org/linux/man-pages/man2/sendfile.2.html">sendfile system call</a>.
+ <p>
+ To understand the impact of sendfile, it is important to understand the common data path for transfer of data from file to socket:
+ <ol>
+ <li>The operating system reads data from the disk into pagecache in kernel space</li>
+ <li>The application reads the data from kernel space into a user-space buffer</li>
+ <li>The application writes the data back into kernel space into a socket buffer</li>
+ <li>The operating system copies the data from the socket buffer to the NIC buffer where it is sent over the network</li>
+ </ol>
+ <p>
+ This is clearly inefficient, there are four copies and two system calls. Using sendfile, this re-copying is avoided by allowing the OS to send the data from pagecache to the network directly. So in this optimized
+ path, only the final copy to the NIC buffer is needed.
+ <p>
+ We expect a common use case to be multiple consumers on a topic. Using the zero-copy optimization above, data is copied into pagecache exactly once and reused on each consumption instead of being stored in memory
+ and copied out to user-space every time it is read. This allows messages to be consumed at a rate that approaches the limit of the network connection.
+ <p>
+ This combination of pagecache and sendfile means that on a Kafka cluster where the consumers are mostly caught up you will see no read activity on the disks whatsoever as they will be serving data entirely from cache.
+ <p>
+ TLS/SSL libraries operate at the user space (in-kernel <code>SSL_sendfile</code> is currently not supported by Kafka). Due to this restriction, <code>sendfile</code> is not used when SSL is enabled. For enabling
+ SSL configuration, refer to <code>security.protocol</code> and <code>security.inter.broker.protocol</code>
+ <p>
+ For more background on the sendfile and zero-copy support in Java, see this <a href="https://developer.ibm.com/articles/j-zerocopy/">article</a>.
+
+ <h4 class="anchor-heading"><a id="design_compression" class="anchor-link"></a><a href="#design_compression">End-to-end Batch Compression</a></h4>
+ <p>
+ In some cases the bottleneck is actually not CPU or disk but network bandwidth. This is particularly true for a data pipeline that needs to send messages between data centers over a wide-area network. Of course,
+ the user can always compress its messages one at a time without any support needed from Kafka, but this can lead to very poor compression ratios as much of the redundancy is due to repetition between messages of
+ the same type (e.g. field names in JSON or user agents in web logs or common string values). Efficient compression requires compressing multiple messages together rather than compressing each message individually.
+ <p>
+ Kafka supports this with an efficient batching format. A batch of messages can be grouped together, compressed, and sent to the server in this form. The broker decompresses the batch in order to validate it. For
+ example, it validates that the number of records in the batch is same as what batch header states. This batch of messages is then written to disk in compressed form. The batch will remain compressed in the log and it will also be transmitted to the
+ consumer in compressed form. The consumer decompresses any compressed data that it receives.
+ <p>
+ Kafka supports GZIP, Snappy, LZ4 and ZStandard compression protocols. More details on compression can be found <a href="https://cwiki.apache.org/confluence/x/S5qoAQ">here</a>.
+
+ <h3 class="anchor-heading"><a id="theproducer" class="anchor-link"></a><a href="#theproducer">4.4 The Producer</a></h3>
+
+ <h4 class="anchor-heading"><a id="design_loadbalancing" class="anchor-link"></a><a href="#design_loadbalancing">Load balancing</a></h4>
+ <p>
+ The producer sends data directly to the broker that is the leader for the partition without any intervening routing tier. To help the producer do this all Kafka nodes can answer a request for metadata about which
+ servers are alive and where the leaders for the partitions of a topic are at any given time to allow the producer to appropriately direct its requests.
+ <p>
+ The client controls which partition it publishes messages to. This can be done at random, implementing a kind of random load balancing, or it can be done by some semantic partitioning function. We expose the interface
+ for semantic partitioning by allowing the user to specify a key to partition by and using this to hash to a partition (there is also an option to override the partition function if need be). For example if the key
+ chosen was a user id then all data for a given user would be sent to the same partition. This in turn will allow consumers to make locality assumptions about their consumption. This style of partitioning is explicitly
+ designed to allow locality-sensitive processing in consumers.
+
+ <h4 class="anchor-heading"><a id="design_asyncsend" class="anchor-link"></a><a href="#design_asyncsend">Asynchronous send</a></h4>
+ <p>
+ Batching is one of the big drivers of efficiency, and to enable batching the Kafka producer will attempt to accumulate data in memory and to send out larger batches in a single request. The batching can be configured
+ to accumulate no more than a fixed number of messages and to wait no longer than some fixed latency bound (say 64k or 10 ms). This allows the accumulation of more bytes to send, and few larger I/O operations on the
+ servers. This buffering is configurable and gives a mechanism to trade off a small amount of additional latency for better throughput.
+ <p>
+ Details on <a href="#producerconfigs">configuration</a> and the <a href="#producerapi">api</a> for the producer can be found
+ elsewhere in the documentation.
+
+ <h3 class="anchor-heading"><a id="theconsumer" class="anchor-link"></a><a href="#theconsumer">4.5 The Consumer</a></h3>
+
+ The Kafka consumer works by issuing "fetch" requests to the brokers leading the partitions it wants to consume. The consumer specifies its offset in the log with each request and receives back a chunk of log
+ beginning from that position. The consumer thus has significant control over this position and can rewind it to re-consume data if need be.
+
+ <h4 class="anchor-heading"><a id="design_pull" class="anchor-link"></a><a href="#design_pull">Push vs. pull</a></h4>
+ <p>
+ An initial question we considered is whether consumers should pull data from brokers or brokers should push data to the consumer. In this respect Kafka follows a more traditional design, shared by most messaging
+ systems, where data is pushed to the broker from the producer and pulled from the broker by the consumer. Some logging-centric systems, such as <a href="https://github.com/facebook/scribe">Scribe</a> and
+ <a href="https://flume.apache.org/">Apache Flume</a>, follow a very different push-based path where data is pushed downstream. There are pros and cons to both approaches. However, a push-based system has difficulty
+ dealing with diverse consumers as the broker controls the rate at which data is transferred. The goal is generally for the consumer to be able to consume at the maximum possible rate; unfortunately, in a push
+ system this means the consumer tends to be overwhelmed when its rate of consumption falls below the rate of production (a denial of service attack, in essence). A pull-based system has the nicer property that
+ the consumer simply falls behind and catches up when it can. This can be mitigated with some kind of backoff protocol by which the consumer can indicate it is overwhelmed, but getting the rate of transfer to
+ fully utilize (but never over-utilize) the consumer is trickier than it seems. Previous attempts at building systems in this fashion led us to go with a more traditional pull model.
+ <p>
+ Another advantage of a pull-based system is that it lends itself to aggressive batching of data sent to the consumer. A push-based system must choose to either send a request immediately or accumulate more data
+ and then send it later without knowledge of whether the downstream consumer will be able to immediately process it. If tuned for low latency, this will result in sending a single message at a time only for the
+ transfer to end up being buffered anyway, which is wasteful. A pull-based design fixes this as the consumer always pulls all available messages after its current position in the log (or up to some configurable max
+ size). So one gets optimal batching without introducing unnecessary latency.
+ <p>
+ The deficiency of a naive pull-based system is that if the broker has no data the consumer may end up polling in a tight loop, effectively busy-waiting for data to arrive. To avoid this we have parameters in our
+ pull request that allow the consumer request to block in a "long poll" waiting until data arrives (and optionally waiting until a given number of bytes is available to ensure large transfer sizes).
+ <p>
+ You could imagine other possible designs which would be only pull, end-to-end. The producer would locally write to a local log, and brokers would pull from that with consumers pulling from them. A similar type of
+ "store-and-forward" producer is often proposed. This is intriguing but we felt not very suitable for our target use cases which have thousands of producers. Our experience running persistent data systems at
+ scale led us to feel that involving thousands of disks in the system across many applications would not actually make things more reliable and would be a nightmare to operate. And in practice we have found that we
+ can run a pipeline with strong SLAs at large scale without a need for producer persistence.
+
+ <h4 class="anchor-heading"><a id="design_consumerposition" class="anchor-link"></a><a href="#design_consumerposition">Consumer Position</a></h4>
+ Keeping track of <i>what</i> has been consumed is, surprisingly, one of the key performance points of a messaging system.
+ <p>
+ Most messaging systems keep metadata about what messages have been consumed on the broker. That is, as a message is handed out to a consumer, the broker either records that fact locally immediately or it may wait
+ for acknowledgement from the consumer. This is a fairly intuitive choice, and indeed for a single machine server it is not clear where else this state could go. Since the data structures used for storage in many
+ messaging systems scale poorly, this is also a pragmatic choice--since the broker knows what is consumed it can immediately delete it, keeping the data size small.
+ <p>
+ What is perhaps not obvious is that getting the broker and consumer to come into agreement about what has been consumed is not a trivial problem. If the broker records a message as <b>consumed</b> immediately every
+ time it is handed out over the network, then if the consumer fails to process the message (say because it crashes or the request times out or whatever) that message will be lost. To solve this problem, many messaging
+ systems add an acknowledgement feature which means that messages are only marked as <b>sent</b> not <b>consumed</b> when they are sent; the broker waits for a specific acknowledgement from the consumer to record the
+ message as <b>consumed</b>. This strategy fixes the problem of losing messages, but creates new problems. First of all, if the consumer processes the message but fails before it can send an acknowledgement then the
+ message will be consumed twice. The second problem is around performance, now the broker must keep multiple states about every single message (first to lock it so it is not given out a second time, and then to mark
+ it as permanently consumed so that it can be removed). Tricky problems must be dealt with, like what to do with messages that are sent but never acknowledged.
+ <p>
+ Kafka handles this differently. Our topic is divided into a set of totally ordered partitions, each of which is consumed by exactly one consumer within each subscribing consumer group at any given time. This means
+ that the position of a consumer in each partition is just a single integer, the offset of the next message to consume. This makes the state about what has been consumed very small, just one number for each partition.
+ This state can be periodically checkpointed. This makes the equivalent of message acknowledgements very cheap.
+ <p>
+ There is a side benefit of this decision. A consumer can deliberately <i>rewind</i> back to an old offset and re-consume data. This violates the common contract of a queue, but turns out to be an essential feature
+ for many consumers. For example, if the consumer code has a bug and is discovered after some messages are consumed, the consumer can re-consume those messages once the bug is fixed.
+
+ <h4 class="anchor-heading"><a id="design_offlineload" class="anchor-link"></a><a href="#design_offlineload">Offline Data Load</a></h4>
+
+ Scalable persistence allows for the possibility of consumers that only periodically consume such as batch data loads that periodically bulk-load data into an offline system such as Hadoop or a relational data
+ warehouse.
+ <p>
+ In the case of Hadoop we parallelize the data load by splitting the load over individual map tasks, one for each node/topic/partition combination, allowing full parallelism in the loading. Hadoop provides the task
+ management, and tasks which fail can restart without danger of duplicate data—they simply restart from their original position.
+
+ <h4 class="anchor-heading"><a id="static_membership" class="anchor-link"></a><a href="#static_membership">Static Membership</a></h4>
+ Static membership aims to improve the availability of stream applications, consumer groups and other applications built on top of the group rebalance protocol.
+ The rebalance protocol relies on the group coordinator to allocate entity ids to group members. These generated ids are ephemeral and will change when members restart and rejoin.
+ For consumer based apps, this "dynamic membership" can cause a large percentage of tasks re-assigned to different instances during administrative operations
+ such as code deploys, configuration updates and periodic restarts. For large state applications, shuffled tasks need a long time to recover their local states before processing
+ and cause applications to be partially or entirely unavailable. Motivated by this observation, Kafka’s group management protocol allows group members to provide persistent entity ids.
+ Group membership remains unchanged based on those ids, thus no rebalance will be triggered.
+ <p>
+ If you want to use static membership,
+ <ul>
+ <li>Upgrade both broker cluster and client apps to 2.3 or beyond, and also make sure the upgraded brokers are using <code>inter.broker.protocol.version</code>
+ of 2.3 or beyond as well.</li>
+ <li>Set the config <code>ConsumerConfig#GROUP_INSTANCE_ID_CONFIG</code> to a unique value for each consumer instance under one group.</li>
+ <li>For Kafka Streams applications, it is sufficient to set a unique <code>ConsumerConfig#GROUP_INSTANCE_ID_CONFIG</code> per KafkaStreams instance,
+ independent of the number of used threads for an instance.</li>
+ </ul>
+ If your broker is on an older version than 2.3, but you choose to set <code>ConsumerConfig#GROUP_INSTANCE_ID_CONFIG</code> on the client side, the application will detect
+ the broker version and then throws an UnsupportedException. If you accidentally configure duplicate ids for different instances,
+ a fencing mechanism on broker side will inform your duplicate client to shutdown immediately by triggering a <code>org.apache.kafka.common.errors.FencedInstanceIdException</code>.
+ For more details, see
+ <a href="https://cwiki.apache.org/confluence/x/kRg0BQ">KIP-345</a>
+
+ <h3 class="anchor-heading"><a id="semantics" class="anchor-link"></a><a href="#semantics">4.6 Message Delivery Semantics</a></h3>
+ <p>
+ Now that we understand a little about how producers and consumers work, let's discuss the semantic guarantees Kafka provides between producer and consumer. Clearly there are multiple possible message delivery
+ guarantees that could be provided:
+ <ul>
+ <li>
+ <i>At most once</i>—Messages may be lost but are never redelivered.
+ </li>
+ <li>
+ <i>At least once</i>—Messages are never lost but may be redelivered.
+ </li>
+ <li>
+ <i>Exactly once</i>—Each message is processed once and only once.
+ </li>
+ </ul>
+
+ It's worth noting that this breaks down into two problems: the durability guarantees for publishing a message and the guarantees when consuming a message.
+ <p>
+ Many systems claim to provide "exactly-once" delivery semantics, but it is important to read the fine print, because sometimes these claims are misleading (i.e. they don't translate to the case where consumers or producers
+ can fail, cases where there are multiple consumer processes, or cases where data written to disk can be lost).
+ <p>
+ Kafka's semantics are straightforward. When publishing a message we have a notion of the message being "committed" to the log. A message is considered committed only when all replicas in the in-sync replicas (ISR) for that
+ partition have applied it to their log. Once a published message is committed, it will not be lost as long as one broker that replicates the partition to which this message was written remains "alive".
+ The definition of committed message and alive partition as well as a description of which types of failures we attempt to handle will be
+ described in more detail in the next section. For now let's assume a perfect, lossless broker and try to understand the guarantees to the producer and consumer. If a producer attempts to publish a message and
+ experiences a network error, it cannot be sure if this error happened before or after the message was committed. This is similar to the semantics of inserting into a database table with an autogenerated key.
+ <p>
+ Prior to 0.11.0.0, if a producer failed to receive a response indicating that a message was committed, it had little choice but to resend the message. This provides at-least-once delivery semantics since the
+ message may be written to the log again during resending if the original request had in fact succeeded. Since 0.11.0.0, the Kafka producer also supports an idempotent delivery option which guarantees that resending
+ will not result in duplicate entries in the log. To achieve this, the broker assigns each producer an ID and deduplicates messages using a sequence number that is sent by the producer along with every message.
+ Also beginning with 0.11.0.0, the producer supports the ability to send messages atomically to multiple topic partitions using transactions, so that either all messages are successfully written or none of them are.
+ <p>
+ Not all use cases require such strong guarantees. For use cases which are latency-sensitive, we allow the producer to specify the durability level it desires. If the producer specifies that it wants to wait on the message
+ being committed, this can take on the order of 10 ms. However the producer can also specify that it wants to perform the send completely asynchronously or that it wants to wait only until the leader (but not
+ necessarily the followers) have the message.
+ <p>
+ Now let's describe the semantics from the point of view of the consumer. All replicas have the exact same log with the same offsets. The consumer controls its position in this log. If the consumer never crashed it
+ could just store this position in memory, but if the consumer fails and we want this topic partition to be taken over by another process, the new process will need to choose an appropriate position from which to start
+ processing. Let's say the consumer reads some messages -- it has several options for processing the messages and updating its position.
+ <ol>
+ <li>It can read the messages, then save its position in the log, and finally process the messages. In this case there is a possibility that the consumer process crashes after saving its position but before saving
+ the output of its message processing. In this case the process that took over processing would start at the saved position even though a few messages prior to that position had not been processed. This corresponds
+ to "at-most-once" semantics as in the case of a consumer failure messages may not be processed.
+ <li>It can read the messages, process the messages, and finally save its position. In this case there is a possibility that the consumer process crashes after processing messages but before saving its position.
+ In this case when the new process takes over the first few messages it receives will already have been processed. This corresponds to the "at-least-once" semantics in the case of consumer failure. In many cases
+ messages have a primary key and so the updates are idempotent (receiving the same message twice just overwrites a record with another copy of itself).
+ </ol>
+ <p>
+ So what about exactly-once semantics? When consuming from a Kafka topic and producing to another topic (as in a <a href="https://kafka.apache.org/documentation/streams">Kafka Streams</a> application), we can
+ leverage the new transactional producer capabilities in 0.11.0.0 that were mentioned above. The consumer's position is stored as a message in an internal topic, so we can write the offset to Kafka in the
+ same transaction as the output topics receiving the processed data. If the transaction is aborted, the consumer's stored position will revert to its old value (although the consumer has to refetch the
+ committed offset because it does not automatically rewind) and the produced data on the output topics will not be visible to other consumers, depending on their "isolation level". In the default
+ "read_uncommitted" isolation level, all messages are visible to consumers even if they were part of an aborted transaction, but in "read_committed" isolation level, the consumer will only return messages
+ from transactions which were committed (and any messages which were not part of a transaction).
+ <p>
+ When writing to an external system, the limitation is in the need to coordinate the consumer's position with what is actually stored as output. The classic way of achieving this would be to introduce a two-phase
+ commit between the storage of the consumer position and the storage of the consumers output. This can be handled more simply and generally by letting the consumer store its offset in the same place as
+ its output. This is better because many of the output systems a consumer might want to write to will not support a two-phase commit. As an example of this, consider a
+ <a href="https://kafka.apache.org/documentation/#connect">Kafka Connect</a> connector which populates data in HDFS along with the offsets of the data it reads so that it is guaranteed that either data and
+ offsets are both updated or neither is. We follow similar patterns for many other data systems which require these stronger semantics and for which the messages do not have a primary key to allow for deduplication.
+ <p>
+ As a result, Kafka supports exactly-once delivery in <a href="https://kafka.apache.org/documentation/streams">Kafka Streams</a>, and the transactional producer and the consumer using read-committed isolation level
+ can be used generally to provide exactly-once delivery when reading, processing and writing data on Kafka topics. Exactly-once delivery for other destination systems generally requires cooperation with such systems,
+ but Kafka provides the primitives which makes implementing this feasible (see also <a href="https://kafka.apache.org/documentation/#connect">Kafka Connect</a>). Otherwise, Kafka guarantees at-least-once delivery
+ by default, and allows the user to implement at-most-once delivery by disabling retries on the producer and committing offsets in the consumer prior to processing a batch of messages.
+
+ <h3 class="anchor-heading"><a id="usingtransactions" class="anchor-link"></a><a href="#usingtransactions">4.7 Using Transactions</a></h3>
+ <p>
+ As mentioned above, the simplest way to get exactly-once semantics from Kafka is to use <a href="https://kafka.apache.org/documentation/streams">Kafka Streams</a>. However, it is also possible to achieve
+ the same transactional guarantees using the Kafka producer and consumer directly by using them in the same way as Kafka Streams does.
+ <p>
+ Kafka transactions are a bit different from transactions in other messaging systems. In Kafka, the consumer and producer are separate, and it is only the producer which is transactional. It is however able to
+ make transactional updates to the consumer's position (confusingly called the "committed offset"), and it is this which gives the overall exactly-once behavior.
+ <p>
+ There are three key aspects to exactly-once processing using the producer and consumer, which match how Kafka Streams works.
+ <ol>
+ <li>The consumer uses partition assignment to ensure that it is the only consumer in the consumer group currently processing each partition.</li>
+ <li>The producer uses transactions so that all the records it produces, and any offsets it updates on behalf of the consumer, are performed atomically.</li>
+ <li>In order to handle transactions properly in combination with rebalancing, it is advisable to use one producer instance for each consumer instance. More complicated and efficient schemes are possible,
+ but at the cost of greater complexity.</li>
+ </ol>
+ <p>
+ In addition, it is generally considered a good practice to use the read-committed isolation level if trying to achieve exactly-once processing. Strictly speaking, the consumer doesn't have to use read-committed
+ isolation level, but if it does not, it will see records from aborted transactions and also open transactions which have not yet completed.
+ <p>
+ The consumer configuration must include <code>isolation.level=read_committed</code> and <code>enable.auto.commit=false</code>. The producer configuration must set <code>transactional.id</code>
+ to the name of the transactional ID to be used, which configures the producer for transactional delivery and also makes sure that a restarted application causes any in-flight transaction from
+ the previous instance to abort. Only the producer has the <code>transactional.id</code> configuration.
+ <p>
+ Here's an example of a <a href="https://github.com/apache/kafka/blob/trunk/tools/src/main/java/org/apache/kafka/tools/TransactionalMessageCopier.java">transactional message copier</a>
+ which uses these principles. It uses a <code>KafkaConsumer</code> to consume records from one topic and a <code>KafkaProducer</code> to produce records to another topic. It uses transactions to ensure
+ that there is no duplication or loss of records as they are copied, provided that the <code>--use-group-metadata</code> option is set.
+ <p>
+ It is important to handle exceptions and aborted transactions correctly. Any records written by the transactional producer will be marked as being part of the transactions, and then when the
+ transaction commits or aborts, transaction marker records are written to indicate the outcome of the transaction. This is how the read-committed consumer does not see records from aborted
+ transactions. However, in the event of a transaction abort, the application's state and in particular the current position of the consumer must be reset explicitly so that it can
+ reprocess the records processed by the aborted transaction.
+ <p>
+ The error handling for transactional producer has been standardized which ensures consistent behavior and clearer error handling patterns. The exception categories are now more precisely defined:
+ <ol>
+ <li><strong>RetriableException</strong>: Temporary exceptions that are retried automatically by the client. These are handled internally and don't bubble up to the application.</li>
+ <li><strong>RefreshRetriableException</strong>: Exceptions requiring metadata refresh before retry. These are handled internally by the client after refreshing metadata and don't bubble up to the application.</li>
+ <li><strong>AbortableException</strong>: Exceptions that require transaction abort and reprocessing. These bubble up to the application, which must handle them by aborting the transaction and resetting the consumer position.</li>
+ <li><strong>ApplicationRecoverableException</strong>: Exceptions that bubble up to the application and require application handling. The application must implement its own recovery strategy, which must include restarting the producer.</li>
+ <li><strong>InvalidConfigurationException</strong>: Configuration-related exceptions that bubble up to the application and require application handling. The producer doesn't need to restart, but the application may choose to restart it.</li>
+ <li><strong>KafkaException</strong>: General Kafka exceptions that don't fit into the above categories. These bubble up to the application for handling.</li>
+ </ol>
+ <p>
+ Example template code for handling transaction exceptions link : <a href="https://github.com/apache/kafka/blob/trunk/examples/src/main/java/kafka/examples/TransactionalClientDemo.java"> Transaction Client Demo</a>
+ <p>
+ A simple policy for handling exceptions and aborted transactions is to discard and recreate the Kafka producer and consumer objects and start afresh. As part of recreating the consumer, the consumer
+ group will rebalance and fetch the last committed offset, which has the effect of rewinding back to the state before the transaction aborted. Alternatively, a more sophisticated application (such as the
+ transactional message copier) can choose not to use <code>KafkaConsumer.committed</code> to retrieve the committed offset from Kafka, and then <code>KafkaConsumer.seek</code> to rewind the current position.
+
+ <h3 class="anchor-heading"><a id="sharegroups" class="anchor-link"></a><a href="#sharegroups">4.8 Share groups</a></h3>
+ <p>
+ Share groups are available as a preview in Apache Kafka 4.1.
+ <p>
+ Share groups are a new type of group, existing alongside traditional consumer groups. Share groups enable Kafka consumers to cooperatively consume and process records from topics.
+ They offer an alternative to traditional consumer groups, particularly when applications require finer-grained sharing of partitions and records.
+ <p>
+ The fundamental differences between a share group and a consumer group are:
+ <ul>
+ <li>The consumers within a share group cooperatively consume records, and partitions may be assigned to multiple consumers.</li>
+ <li>The number of consumers in a share group can exceed the number of partitions in a topic.</li>
+ <li>Records are acknowledged individually, though the system is optimized for batch processing to improve efficiency.</li>
+ <li>Delivery attempts to consumers in a share group are counted, which enables automated handling of unprocessable records.</li>
+ </ul>
+ <p>
+ All consumers in the same share group subscribed to the same topic will cooperatively consume the records of that topic. If a topic is accessed by consumers in multiple share groups, each share group
+ consumes from that topic independently of the others.
+ <p>
+ Each consumer can dynamically set its list of subscribed topics. In practice, all consumers within a share group typically subscribe to the same topic or topics.
+ <p>
+ When a consumer in a share-group fetches records, it receives available records from any of the topic-partitions matching its subscriptions. Records are acquired for delivery to this consumer with a time-limited
+ acquisition lock. While a record is acquired, it is unavailable to other consumers.
+ <p>By default, the lock duration is 30 seconds, but you can control it using the group configuration parameter <code>share.record.lock.duration.ms</code>. The lock is released automatically once its
+ duration elapses, making the record available to another consumer. A consumer holding the lock can handle the record in the following ways:
+ <ul>
+ <li>Acknowledge successful processing of the record.</li>
+ <li>Release the record, making it available for another delivery attempt.</li>
+ <li>Reject the record, indicating it's unprocessable and preventing further delivery attempts for that record.</li>
+ <li>Do nothing, in which case the lock is automatically released when its duration expires.</li>
+ </ul>
+ <p>
+ The Kafka cluster limits the number of records acquired for consumers for each topic-partition within a share group. Once this limit is reached, fetching operations will temporarily yield no further records
+ until the number of acquired records decreases (as locks naturally time out). This limit is controlled by the broker configuration property <code>group.share.partition.max.record.locks</code>. By limiting
+ the duration of the acquisition lock and automatically releasing the locks, the broker ensures delivery progresses even in the presence of consumer failures.
+
+ <h3 class="anchor-heading"><a id="replication" class="anchor-link"></a><a href="#replication">4.9 Replication</a></h3>
+ <p>
+ Kafka replicates the log for each topic's partitions across a configurable number of servers (you can set this replication factor on a topic-by-topic basis). This allows automatic failover to these replicas when a
+ server in the cluster fails so messages remain available in the presence of failures.
+ <p>
+ Other messaging systems provide some replication-related features, but, in our (totally biased) opinion, this appears to be a tacked-on thing, not heavily used, and with large downsides: replicas are inactive,
+ throughput is heavily impacted, it requires fiddly manual configuration, etc. Kafka is meant to be used with replication by default—in fact we implement un-replicated topics as replicated topics where the
+ replication factor is one.
+ <p>
+ The unit of replication is the topic partition. Under non-failure conditions, each partition in Kafka has a single leader and zero or more followers. The total number of replicas including the leader constitute the
+ replication factor. All writes go to the leader of the partition, and reads can go to the leader or the followers of the partition. Typically, there are many more partitions than brokers and the leaders are evenly distributed among brokers. The logs on the followers are
+ identical to the leader's log—all have the same offsets and messages in the same order (though, of course, at any given time the leader may have a few as-yet unreplicated messages at the end of its log).
+ <p>
+ Followers consume messages from the leader just as a normal Kafka consumer would and apply them to their own log. Having the followers pull from the leader has the nice property of allowing the follower to naturally
+ batch together log entries they are applying to their log.
+ <p>
+ As with most distributed systems, automatically handling failures requires a precise definition of what it means for a node to be "alive." In Kafka, a special node
+ known as the "controller" is responsible for managing the registration of brokers in the cluster. Broker liveness has two conditions:
+ <ol>
+ <li>Brokers must maintain an active session with the controller in order to receive regular metadata updates.</li>
+ <li>Brokers acting as followers must replicate the writes from the leader and not fall "too far" behind.</li>
+ </ol>
+ <p>
+ What is meant by an "active session" depends on the cluster configuration. For KRaft clusters, an active session is maintained by
+ sending periodic heartbeats to the controller. If the controller fails to receive a heartbeat before the timeout configured by
+ <code>broker.session.timeout.ms</code> expires, then the node is considered offline.
+ <p>
+ We refer to nodes satisfying these two conditions as being "in sync" to avoid the vagueness of "alive" or "failed". The leader keeps track of the set of "in sync" replicas,
+ which is known as the ISR. If either of these conditions fail to be satisfied, then the broker will be removed from the ISR. For example,
+ if a follower dies, then the controller will notice the failure through the loss of its session, and will remove the broker from the ISR.
+ On the other hand, if the follower lags too far behind the leader but still has an active session, then the leader can also remove it from the ISR.
+ The determination of lagging replicas is controlled through the <code>replica.lag.time.max.ms</code> configuration.
+ Replicas that cannot catch up to the end of the log on the leader within the max time set by this configuration are removed from the ISR.
+ <p>
+ In distributed systems terminology we only attempt to handle a "fail/recover" model of failures where nodes suddenly cease working and then later recover (perhaps without knowing that they have died). Kafka does not
+ handle so-called "Byzantine" failures in which nodes produce arbitrary or malicious responses (perhaps due to bugs or foul play).
+ <p>
+ Only committed messages are ever given out to the consumer. This means that the consumer need not worry about potentially seeing a message that could be lost if the leader fails. Producers, on the other hand,
+ have the option of either waiting for the message to be committed or not, depending on their preference for tradeoff between latency and durability. This preference is controlled by the <code>acks</code> setting that the
+ producer uses.
+ Note that topics have a setting for the minimum number of in-sync replicas (<code>min.insync.replicas</code>) that is checked when the producer requests acknowledgment that a message
+ has been written to the full set of in-sync replicas. If a less stringent acknowledgment is requested by the producer, then the message is committed asynchronously across the set of in-sync replicas if
+ <code>acks=0</code>, or synchronously only on the leader if <code>acks=1</code>.
+ Regardless of the <code>acks</code> setting, the messages will not be visible to the consumers until all the following conditions are met:
+ <ol>
+ <li>The messages are replicated to all the in-sync replicas.</li>
+ <li>The number of the in-sync replicas is no less than the <code>min.insync.replicas</code> setting.</li>
+ </ol>
+ <p>
+ The guarantee that Kafka offers is that a committed message will not be lost, as long as there is at least one in sync replica alive, at all times.
+ <p>
+ Kafka will remain available in the presence of node failures after a short fail-over period, but may not remain available in the presence of network partitions.
+
+ <h4><a id="design_replicatedlog" href="#design_replicatedlog">Replicated Logs: Quorums, ISRs, and State Machines (Oh my!)</a></h4>
+
+ At its heart a Kafka partition is a replicated log. The replicated log is one of the most basic primitives in distributed data systems, and there are many approaches for implementing one. A replicated log can be
+ used by other systems as a primitive for implementing other distributed systems in the <a href="https://en.wikipedia.org/wiki/State_machine_replication">state-machine style</a>.
+ <p>
+ A replicated log models the process of coming into consensus on the order of a series of values (generally numbering the log entries 0, 1, 2, ...). There are many ways to implement this, but the simplest and fastest
+ is with a leader who chooses the ordering of values provided to it. As long as the leader remains alive, all followers need to only copy the values and ordering the leader chooses.
+ <p>
+ Of course if leaders didn't fail we wouldn't need followers! When the leader does die we need to choose a new leader from among the followers. But followers themselves may fall behind or crash so we must ensure we
+ choose an up-to-date follower. The fundamental guarantee a log replication algorithm must provide is that if we tell the client a message is committed, and the leader fails, the new leader we elect must also have
+ that message. This yields a tradeoff: if the leader waits for more followers to acknowledge a message before declaring it committed then there will be more potentially electable leaders.
+ <p>
+ If you choose the number of acknowledgements required and the number of logs that must be compared to elect a leader such that there is guaranteed to be an overlap, then this is called a Quorum.
+ <p>
+ A common approach to this tradeoff is to use a majority vote for both the commit decision and the leader election. This is not what Kafka does, but let's explore it anyway to understand the tradeoffs. Let's say we
+ have 2<i>f</i>+1 replicas. If <i>f</i>+1 replicas must receive a message prior to a commit being declared by the leader, and if we elect a new leader by electing the follower with the most complete log from at least
+ <i>f</i>+1 replicas, then, with no more than <i>f</i> failures, the leader is guaranteed to have all committed messages. This is because among any <i>f</i>+1 replicas, there must be at least one replica that contains
+ all committed messages. That replica's log will be the most complete and therefore will be selected as the new leader. There are many remaining details that each algorithm must handle (such as precisely defined what
+ makes a log more complete, ensuring log consistency during leader failure or changing the set of servers in the replica set) but we will ignore these for now.
+ <p>
+ This majority vote approach has a very nice property: the latency is dependent on only the fastest servers. That is, if the replication factor is three, the latency is determined by the faster follower not the slower one.
+ <p>
+ There are a rich variety of algorithms in this family including ZooKeeper's
+ <a href="https://web.archive.org/web/20140602093727/https://www.stanford.edu/class/cs347/reading/zab.pdf">Zab</a>,
+ <a href="https://www.usenix.org/system/files/conference/atc14/atc14-paper-ongaro.pdf">Raft</a>,
+ and <a href="https://pmg.csail.mit.edu/papers/vr-revisited.pdf">Viewstamped Replication</a>.
+ The most similar academic publication we are aware of to Kafka's actual implementation is
+ <a href="https://research.microsoft.com/apps/pubs/default.aspx?id=66814">PacificA</a> from Microsoft.
+ <p>
+ The downside of majority vote is that it doesn't take many failures to leave you with no electable leaders. To tolerate one failure requires three copies of the data, and to tolerate two failures requires five copies
+ of the data. In our experience having only enough redundancy to tolerate a single failure is not enough for a practical system, but doing every write five times, with 5x the disk space requirements and 1/5th the
+ throughput, is not very practical for large volume data problems. This is likely why quorum algorithms more commonly appear for shared cluster configuration such as ZooKeeper but are less common for primary data
+ storage. For example in HDFS the namenode's high-availability feature is built on a <a href="https://blog.cloudera.com/blog/2012/10/quorum-based-journaling-in-cdh4-1">majority-vote-based journal</a>, but this more
+ expensive approach is not used for the data itself.
+ <p>
+ Kafka takes a slightly different approach to choosing its quorum set. Instead of majority vote, Kafka dynamically maintains a set of in-sync replicas (ISR) that are caught-up to the leader. Only members of this set
+ are eligible for election as leader. A write to a Kafka partition is not considered committed until <i>all</i> in-sync replicas have received the write. This ISR set is persisted in the cluster metadata whenever it changes.
+ Because of this, any replica in the ISR is eligible to be elected leader. This is an important factor for Kafka's usage model where there are many partitions and ensuring leadership balance is important.
+ With this ISR model and <i>f+1</i> replicas, a Kafka topic can tolerate <i>f</i> failures without losing committed messages.
+ <p>
+ For most use cases we hope to handle, we think this tradeoff is a reasonable one. In practice, to tolerate <i>f</i> failures, both the majority vote and the ISR approach will wait for the same number of replicas to
+ acknowledge before committing a message (e.g. to survive one failure a majority quorum needs three replicas and one acknowledgement and the ISR approach requires two replicas and one acknowledgement).
+ The ability to commit without the slowest servers is an advantage of the majority vote approach. However, we think it is ameliorated by allowing the client to choose whether they block on the message commit or not,
+ and the additional throughput and disk space due to the lower required replication factor is worth it.
+ <p>
+ Another important design distinction is that Kafka does not require that crashed nodes recover with all their data intact. It is not uncommon for replication algorithms in this space to depend on the existence of
+ "stable storage" that cannot be lost in any failure-recovery scenario without potential consistency violations. There are two primary problems with this assumption. First, disk errors are the most common problem we
+ observe in real operation of persistent data systems and they often do not leave data intact. Secondly, even if this were not a problem, we do not want to require the use of fsync on every write for our consistency
+ guarantees as this can reduce performance by two to three orders of magnitude. Our protocol for allowing a replica to rejoin the ISR ensures that before rejoining, it must fully re-sync again even if it lost unflushed
+ data in its crash.
+
+ <h4><a id="design_uncleanleader" href="#design_uncleanleader">Unclean leader election: What if they all die?</a></h4>
+
+ Note that Kafka's guarantee with respect to data loss is predicated on at least one replica remaining in sync. If all the nodes replicating a partition die, this guarantee no longer holds.
+ <p>
+ However a practical system needs to do something reasonable when all the replicas die. If you are unlucky enough to have this occur, it is important to consider what will happen. There are two behaviors that could be
+ implemented:
+ <ol>
+ <li>Wait for a replica in the ISR to come back to life and choose this replica as the leader (hopefully it still has all its data).
+ <li>Choose the first replica (not necessarily in the ISR) that comes back to life as the leader.
+ </ol>
+ <p>
+ This is a simple tradeoff between availability and consistency. If we wait for replicas in the ISR, then we will remain unavailable as long as those replicas are down. If such replicas were destroyed or their data
+ was lost, then we are permanently down. If, on the other hand, a non-in-sync replica comes back to life and we allow it to become leader, then its log becomes the source of truth even though it is not guaranteed to
+ have every committed message. By default from version 0.11.0.0, Kafka chooses the first strategy and favor waiting for a consistent replica. This behavior can be changed using
+ configuration property <code>unclean.leader.election.enable</code>, to support use cases where uptime is preferable to consistency.
+ <p>
+ This dilemma is not specific to Kafka. It exists in any quorum-based scheme. For example in a majority voting scheme, if a majority of servers suffer a permanent failure, then you must either choose to lose 100% of
+ your data or violate consistency by taking what remains on an existing server as your new source of truth.
+
+
+ <h4 class="anchor-heading"><a id="design_ha" class="anchor-link"></a><a href="#design_ha">Availability and Durability Guarantees</a></h4>
+
+ When writing to Kafka, producers can choose whether they wait for the message to be acknowledged by 0,1 or all (-1) replicas.
+ Note that "acknowledgement by all replicas" does not guarantee that the full set of assigned replicas have received the message. By default, when acks=all, acknowledgement happens as soon as all the current in-sync
+ replicas have received the message. For example, if a topic is configured with only two replicas and one fails (i.e., only one in sync replica remains), then writes that specify acks=all will succeed. However, these
+ writes could be lost if the remaining replica also fails.
+
+ Although this ensures maximum availability of the partition, this behavior may be undesirable to some users who prefer durability over availability. Therefore, we provide two topic configurations that can be
+ used to prefer message durability over availability:
+ <ol>
+ <li> Disable unclean leader election - if all replicas become unavailable, then the partition will remain unavailable until the most recent leader becomes available again. This effectively prefers unavailability
+ over the risk of message loss. See the previous section on Unclean Leader Election for clarification. </li>
+ <li> Specify a minimum ISR size - the partition will only accept writes if the size of the ISR is above a certain minimum, in order to prevent the loss of messages that were written to just a single replica,
+ which subsequently becomes unavailable. This setting only takes effect if the producer uses acks=all and guarantees that the message will be acknowledged by at least this many in-sync replicas.
+ This setting offers a trade-off between consistency and availability. A higher setting for minimum ISR size guarantees better consistency since the message is guaranteed to be written to more replicas which reduces
+ the probability that it will be lost. However, it reduces availability since the partition will be unavailable for writes if the number of in-sync replicas drops below the minimum threshold. </li>
+ </ol>
+
+
+ <h4 class="anchor-heading"><a id="design_replicamanagment" class="anchor-link"></a><a href="#design_replicamanagment">Replica Management</a></h4>
+
+ The above discussion on replicated logs really covers only a single log, i.e. one topic partition. However a Kafka cluster will manage hundreds or thousands of these partitions. We attempt to balance partitions
+ within a cluster in a round-robin fashion to avoid clustering all partitions for high-volume topics on a small number of nodes. Likewise we try to balance leadership so that each node is the leader for a proportional
+ share of its partitions.
+ <p>
+ It is also important to optimize the leadership election process as that is the critical window of unavailability. A naive implementation of leader election would end up running an election per partition for all
+ partitions a node hosted when that node failed. As discussed above in the section on <a href="#replication">replication</a>, Kafka clusters have a special role known as the "controller" which is
+ responsible for managing the registration of brokers. If the controller detects the failure of a broker, it is responsible for electing one of the remaining members of the ISR to serve as the new leader.
+ The result is that we are able to batch together many of the required leadership change notifications which makes the election process far cheaper and faster for a large number
+ of partitions. If the controller itself fails, then another controller will be elected.
+
+ <h3 class="anchor-heading"><a id="compaction" class="anchor-link"></a><a href="#compaction">4.10 Log Compaction</a></h3>
+
+ Log compaction ensures that Kafka will always retain at least the last known value for each message key within the log of data for a single topic partition. It addresses use cases and scenarios such as restoring
+ state after application crashes or system failure, or reloading caches after application restarts during operational maintenance. Let's dive into these use cases in more detail and then describe how compaction works.
+ <p>
+ So far we have described only the simpler approach to data retention where old log data is discarded after a fixed period of time or when the log reaches some predetermined size. This works well for temporal event
+ data such as logging where each record stands alone. However an important class of data streams are the log of changes to keyed, mutable data (for example, the changes to a database table).
+ <p>
+ Let's discuss a concrete example of such a stream. Say we have a topic containing user email addresses; every time a user updates their email address we send a message to this topic using their user id as the
+ primary key. Now say we send the following messages over some time period for a user with id 123, each message corresponding to a change in email address (messages for other ids are omitted):
+ <pre class="line-numbers"><code class="language-text">123 => bill@microsoft.com
+ .
+ .
+ .
+123 => bill@gatesfoundation.org
+ .
+ .
+ .
+123 => bill@gmail.com</code></pre>
+ Log compaction gives us a more granular retention mechanism so that we are guaranteed to retain at least the last update for each primary key (e.g. <code>bill@gmail.com</code>). By doing this we guarantee that the
+ log contains a full snapshot of the final value for every key not just keys that changed recently. This means downstream consumers can restore their own state off this topic without us having to retain a complete
+ log of all changes.
+ <p>
+ Let's start by looking at a few use cases where this is useful, then we'll see how it can be used.
+ <ol>
+ <li><i>Database change subscription</i>. It is often necessary to have a data set in multiple data systems, and often one of these systems is a database of some kind (either a RDBMS or perhaps a new-fangled key-value
+ store). For example you might have a database, a cache, a search cluster, and a Hadoop cluster. Each change to the database will need to be reflected in the cache, the search cluster, and eventually in Hadoop.
+ In the case that one is only handling the real-time updates you only need recent log. But if you want to be able to reload the cache or restore a failed search node you may need a complete data set.
+ <li><i>Event sourcing</i>. This is a style of application design which co-locates query processing with application design and uses a log of changes as the primary store for the application.
+ <li><i>Journaling for high-availability</i>. A process that does local computation can be made fault-tolerant by logging out changes that it makes to its local state so another process can reload these changes and
+ carry on if it should fail. A concrete example of this is handling counts, aggregations, and other "group by"-like processing in a stream query system. Samza, a real-time stream-processing framework,
+ <a href="https://samza.apache.org/learn/documentation/0.7.0/container/state-management.html">uses this feature</a> for exactly this purpose.
+ </ol>
+ In each of these cases one needs primarily to handle the real-time feed of changes, but occasionally, when a machine crashes or data needs to be re-loaded or re-processed, one needs to do a full load.
+ Log compaction allows feeding both of these use cases off the same backing topic.
+
+ This style of usage of a log is described in more detail in <a href="https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying">this blog post</a>.
+ <p>
+ The general idea is quite simple. If we had infinite log retention, and we logged each change in the above cases, then we would have captured the state of the system at each time from when it first began.
+ Using this complete log, we could restore to any point in time by replaying the first N records in the log. This hypothetical complete log is not very practical for systems that update a single record many times
+ as the log will grow without bound even for a stable dataset. The simple log retention mechanism which throws away old updates will bound space but the log is no longer a way to restore the current state—now
+ restoring from the beginning of the log no longer recreates the current state as old updates may not be captured at all.
+ <p>
+ Log compaction is a mechanism to give finer-grained per-record retention, rather than the coarser-grained time-based retention. The idea is to selectively remove records where we have a more recent update with the
+ same primary key. This way the log is guaranteed to have at least the last state for each key.
+ <p>
+ This retention policy can be set per-topic, so a single cluster can have some topics where retention is enforced by size or time and other topics where retention is enforced by compaction.
+ <p>
+ This functionality is inspired by one of LinkedIn's oldest and most successful pieces of infrastructure—a database changelog caching service called <a href="https://github.com/linkedin/databus">Databus</a>.
+ Unlike most log-structured storage systems Kafka is built for subscription and organizes data for fast linear reads and writes. Unlike Databus, Kafka acts as a source-of-truth store so it is useful even in
+ situations where the upstream data source would not otherwise be replayable.
+
+ <h4 class="anchor-heading"><a id="design_compactionbasics" class="anchor-link"></a><a href="#design_compactionbasics">Log Compaction Basics</a></h4>
+
+ Here is a high-level picture that shows the logical structure of a Kafka log with the offset for each message.
+ <p>
+ <img class="centered" src="/{{version}}/images/log_cleaner_anatomy.png">
+ <p>
+ The head of the log is identical to a traditional Kafka log. It has dense, sequential offsets and retains all messages. Log compaction adds an option for handling the tail of the log. The picture above shows a log
+ with a compacted tail. Note that the messages in the tail of the log retain the original offset assigned when they were first written—that never changes. Note also that all offsets remain valid positions in
+ the log, even if the message with that offset has been compacted away; in this case this position is indistinguishable from the next highest offset that does appear in the log. For example, in the picture above the
+ offsets 36, 37, and 38 are all equivalent positions and a read beginning at any of these offsets would return a message set beginning with 38.
+ <p>
+ Compaction also allows for deletes. A message with a key and a null payload will be treated as a delete from the log. Such a record is sometimes referred to as a <i>tombstone</i>. This delete marker will cause any prior message with that key to be removed (as would any new
+ message with that key), but delete markers are special in that they will themselves be cleaned out of the log after a period of time to free up space. The point in time at which deletes are no longer retained is
+ marked as the "delete retention point" in the above diagram.
+ <p>
+ The compaction is done in the background by periodically recopying log segments. Cleaning does not block reads and can be throttled to use no more than a configurable amount of I/O throughput to avoid impacting
+ producers and consumers. The actual process of compacting a log segment looks something like this:
+ <p>
+ <img class="centered" src="/{{version}}/images/log_compaction.png">
+ <p>
+ <h4 class="anchor-heading">
+ <a class="anchor-link" id="design_compactionguarantees" href="#design_compactionguarantees"></a>
+ <a href="#design_compactionguarantees">What guarantees does log compaction provide</a>?
+ </h4>
+
+ Log compaction guarantees the following:
+ <ol>
+ <li>Any consumer that stays caught-up to within the head of the log will see every message that is written; these messages will have sequential offsets. The topic's <code>min.compaction.lag.ms</code> can be used to
+ guarantee the minimum length of time must pass after a message is written before it could be compacted. I.e. it provides a lower bound on how long each message will remain in the (uncompacted) head.
+ The topic's <code>max.compaction.lag.ms</code> can be used to guarantee the maximum delay between the time a message is written and the time the message becomes eligible for compaction.
+ <li>Ordering of messages is always maintained. Compaction will never re-order messages, just remove some.
+ <li>The offset for a message never changes. It is the permanent identifier for a position in the log.
+ <li>Any consumer progressing from the start of the log will see at least the final state of all records in the order they were written. Additionally, all delete markers for deleted records will be seen, provided
+ the consumer reaches the head of the log in a time period less than the topic's <code>delete.retention.ms</code> setting (the default is 24 hours). In other words: since the removal of delete markers happens
+ concurrently with reads, it is possible for a consumer to miss delete markers if it lags by more than <code>delete.retention.ms</code>.
+ </ol>
+
+ <h4 class="anchor-heading"><a id="design_compactiondetails" class="anchor-link"></a><a href="#design_compactiondetails">Log Compaction Details</a></h4>
+
+ Log compaction is handled by the log cleaner, a pool of background threads that recopy log segment files, removing records whose key appears in the head of the log. Each compactor thread works as follows:
+ <ol>
+ <li>It chooses the log that has the highest ratio of log head to log tail
+ <li>It creates a succinct summary of the last offset for each key in the head of the log
+ <li>It recopies the log from beginning to end removing keys which have a later occurrence in the log. New, clean segments are swapped into the log immediately so the additional disk space required is just one
+ additional log segment (not a fully copy of the log).
+ <li>The summary of the log head is essentially just a space-compact hash table. It uses exactly 24 bytes per entry. As a result with 8GB of cleaner buffer one cleaner iteration can clean around 366GB of log head
+ (assuming 1k messages).
+ </ol>
+ <p>
+ <h4 class="anchor-heading"><a id="design_compactionconfig" class="anchor-link"></a><a href="#design_compactionconfig">Configuring The Log Cleaner</a></h4>
+
+ The log cleaner is enabled by default. This will start the pool of cleaner threads.
+ To enable log cleaning on a particular topic, add the log-specific property
+ <pre class="language-text"><code>log.cleanup.policy=compact</code></pre>
+
+ The <code>log.cleanup.policy</code> property is a broker configuration setting defined
+ in the broker's <code>server.properties</code> file; it affects all of the topics
+ in the cluster that do not have a configuration override in place as documented
+ <a href="/documentation.html#brokerconfigs">here</a>.
+
+ The log cleaner can be configured to retain a minimum amount of the uncompacted "head" of the log. This is enabled by setting the compaction time lag.
+ <pre class="language-text"><code>log.cleaner.min.compaction.lag.ms</code></pre>
+
+ This can be used to prevent messages newer than a minimum message age from being subject to compaction. If not set, all log segments are eligible for compaction except for the last segment, i.e. the one currently
+ being written to. The active segment will not be compacted even if all of its messages are older than the minimum compaction time lag.
+
+ The log cleaner can be configured to ensure a maximum delay after which the uncompacted "head" of the log becomes eligible for log compaction.
+ <pre class="language-text"><code>log.cleaner.max.compaction.lag.ms</code></pre>
+
+ This can be used to prevent log with low produce rate from remaining ineligible for compaction for an unbounded duration. If not set, logs that do not exceed min.cleanable.dirty.ratio are not compacted.
+ Note that this compaction deadline is not a hard guarantee since it is still subjected to the availability of log cleaner threads and the actual compaction time.
+ You will want to monitor the uncleanable-partitions-count, max-clean-time-secs and max-compaction-delay-secs metrics.
+
+ <p>
+ Further cleaner configurations are described <a href="/documentation.html#brokerconfigs">here</a>.
+
+ <h3 class="anchor-heading"><a id="design_quotas" class="anchor-link"></a><a href="#design_quotas">4.11 Quotas</a></h3>
+ <p>
+ Kafka cluster has the ability to enforce quotas on requests to control the broker resources used by clients. Two types
+ of client quotas can be enforced by Kafka brokers for each group of clients sharing a quota:
+ </p>
+ <ol>
+ <li>Network bandwidth quotas define byte-rate thresholds (since 0.9)</li>
+ <li>Request rate quotas define CPU utilization thresholds as a percentage of network and I/O threads (since 0.11)</li>
+ </ol>
+
+ <h4 class="anchor-heading">
+ <a class="anchor-link" id="design_quotasnecessary" href="#design_quotasnecessary"></a>
+ <a href="#design_quotasnecessary">Why are quotas necessary</a>?
+ </h4>
+ <p>
+ It is possible for producers and consumers to produce/consume very high volumes of data or generate requests at a very high
+ rate and thus monopolize broker resources, cause network saturation and generally DOS other clients and the brokers themselves.
+ Having quotas protects against these issues and is all the more important in large multi-tenant clusters where a small set of badly behaved clients can degrade user experience for the well behaved ones.
+ In fact, when running Kafka as a service this even makes it possible to enforce API limits according to an agreed upon contract.
+ </p>
+ <h4 class="anchor-heading"><a id="design_quotasgroups" class="anchor-link"></a><a href="#design_quotasgroups">Client groups</a></h4>
+ The identity of Kafka clients is the user principal which represents an authenticated user in a secure cluster. In a cluster that supports unauthenticated clients, user principal is a grouping of unauthenticated
+ users
+ chosen by the broker using a configurable <code>PrincipalBuilder</code>. Client-id is a logical grouping of clients with a meaningful name chosen by the client application. The tuple (user, client-id) defines
+ a secure logical group of clients that share both user principal and client-id.
+ <p>
+ Quotas can be applied to (user, client-id), user or client-id groups. For a given connection, the most specific quota matching the connection is applied. All connections of a quota group share the quota configured for the group.
+ For example, if (user="test-user", client-id="test-client") has a produce quota of 10MB/sec, this is shared across all producer instances of user "test-user" with the client-id "test-client".
+ </p>
+ <h4 class="anchor-heading"><a id="design_quotasconfig" class="anchor-link"></a><a href="#design_quotasconfig">Quota Configuration</a></h4>
+ <p>
+ Quota configuration may be defined for (user, client-id), user and client-id groups. It is possible to override the default quota at any of the quota levels that needs a higher (or even lower) quota.
+ The mechanism is similar to the per-topic log config overrides.
+ User and (user, client-id) quota overrides are written to the metadata log.
+ These overrides are read by all brokers and are effective immediately. This lets us change quotas without having to do a rolling restart of the entire cluster. See <a href="#quotas">here</a> for details.
+ Default quotas for each group may also be updated dynamically using the same mechanism.
+ </p>
+ <p>
+ The order of precedence for quota configuration is:
+ </p>
+ <ol>
+ <li>matching user and client-id quotas</li>
+ <li>matching user and default client-id quotas</li>
+ <li>matching user quota</li>
+ <li>default user and matching client-id quotas</li>
+ <li>default user and default client-id quotas</li>
+ <li>default user quota</li>
+ <li>matching client-id quota</li>
+ <li>default client-id quota</li>
+ </ol>
+ <h4 class="anchor-heading"><a id="design_quotasbandwidth" class="anchor-link"></a><a href="#design_quotasbandwidth">Network Bandwidth Quotas</a></h4>
+ <p>
+ Network bandwidth quotas are defined as the byte rate threshold for each group of clients sharing a quota.
+ By default, each unique client group receives a fixed quota in bytes/sec as configured by the cluster.
+ This quota is defined on a per-broker basis. Each group of clients can publish/fetch a maximum of X bytes/sec
+ per broker before clients are throttled.
+ </p>
+ <h4 class="anchor-heading"><a id="design_quotascpu" class="anchor-link"></a><a href="#design_quotascpu">Request Rate Quotas</a></h4>
+ <p>
+ Request rate quotas are defined as the percentage of time a client can utilize on request handler I/O
+ threads and network threads of each broker within a quota window. A quota of <code>n%</code> represents
+ <code>n%</code> of one thread, so the quota is out of a total capacity of <code>((num.io.threads + num.network.threads) * 100)%</code>.
+ Each group of clients may use a total percentage of upto <code>n%</code> across all I/O and network threads in a quota
+ window before being throttled. Since the number of threads allocated for I/O and network threads are typically based
+ on the number of cores available on the broker host, request rate quotas represent the total percentage of CPU
+ that may be used by each group of clients sharing the quota.
+ </p>
+ <h4 class="anchor-heading"><a id="design_quotasenforcement" class="anchor-link"></a><a href="#design_quotasenforcement">Enforcement</a></h4>
+ <p>
+ By default, each unique client group receives a fixed quota as configured by the cluster.
+ This quota is defined on a per-broker basis. Each client can utilize this quota per broker before it gets throttled. We decided that defining these quotas per broker is much better than
+ having a fixed cluster wide bandwidth per client because that would require a mechanism to share client quota usage among all the brokers. This can be harder to get right than the quota implementation itself!
+ </p>
+ <p>
+ How does a broker react when it detects a quota violation? In our solution, the broker first computes the amount of delay needed to bring the violating client under its quota
+ and returns a response with the delay immediately. In case of a fetch request, the response will not contain any data. Then, the broker mutes the channel to the client,
+ not to process requests from the client anymore, until the delay is over. Upon receiving a response with a non-zero delay duration, the Kafka client will also refrain from
+ sending further requests to the broker during the delay. Therefore, requests from a throttled client are effectively blocked from both sides.
+ Even with older client implementations that do not respect the delay response from the broker, the back pressure applied by the broker via muting its socket channel
+ can still handle the throttling of badly behaving clients. Those clients who sent further requests to the throttled channel will receive responses only after the delay is over.
+ </p>
+ <p>
+ Byte-rate and thread utilization are measured over multiple small windows (e.g. 30 windows of 1 second each) in order to detect and correct quota violations quickly. Typically, having large measurement windows
+ (for e.g. 10 windows of 30 seconds each) leads to large bursts of traffic followed by long delays which is not great in terms of user experience.
+ </p>
+</script>
+
+<div class="p-design"></div>
diff --git a/41/docker.html b/41/docker.html
new file mode 100644
index 000000000..ef747199e
--- /dev/null
+++ b/41/docker.html
@@ -0,0 +1,58 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<script>
+ <!--#include virtual="js/templateData.js" -->
+</script>
+
+<script id="docker-template" type="text/x-handlebars-template">
+ <h4 class="anchor-heading">JVM Based Apache Kafka Docker Image</h4>
+
+ <p>
+ <a href="https://www.docker.com/">Docker</a> is a popular container runtime. Docker images for the JVM based Apache Kafka can be found on <a href="https://hub.docker.com/r/apache/kafka">Docker Hub</a> and are available from version 3.7.0.
+ </p>
+
+ <p> Docker image can be pulled from Docker Hub using the following command: </p>
+ <pre><code class="language-bash">$ docker pull apache/kafka:{{fullDotVersion}}</code></pre>
+ <p> If you want to fetch the latest version of the Docker image use following command: </p>
+ <pre><code class="language-bash">$ docker pull apache/kafka:latest</code></pre>
+ <p> To start the Kafka container using this Docker image with default configs and on default port 9092: </p>
+ <pre><code class="language-bash">$ docker run -p 9092:9092 apache/kafka:{{fullDotVersion}}</code></pre>
+
+ <h4 class="anchor-heading">GraalVM Based Native Apache Kafka Docker Image</h4>
+
+ <p>
+ Docker images for the GraalVM Based Native Apache Kafka can be found on <a href="https://hub.docker.com/r/apache/kafka-native">Docker Hub</a> and are available from version 3.8.0.<br>
+ NOTE: This image is experimental and intended for local development and testing purposes only; it is not recommended for production use.
+ </p>
+
+ <p> Docker image can be pulled from Docker Hub using the following command: </p>
+ <pre><code class="language-bash">$ docker pull apache/kafka-native:{{fullDotVersion}}</code></pre>
+ <p> If you want to fetch the latest version of the Docker image use following command: </p>
+ <pre><code class="language-bash">$ docker pull apache/kafka-native:latest</code></pre>
+ <p> To start the Kafka container using this Docker image with default configs and on default port 9092: </p>
+ <pre><code class="language-bash">$ docker run -p 9092:9092 apache/kafka-native:{{fullDotVersion}}</code></pre>
+
+
+ <h4 class="anchor-heading">Usage guide</h4>
+
+ <p>
+ Detailed instructions for using the Docker image are mentioned <a href="https://github.com/apache/kafka/blob/trunk/docker/examples/README.md">here</a>.
+ </p>
+</script>
+
+<div class="p-docker"></div>
\ No newline at end of file
diff --git a/41/documentation.html b/41/documentation.html
new file mode 100644
index 000000000..e13042ddd
--- /dev/null
+++ b/41/documentation.html
@@ -0,0 +1,124 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<script><!--#include virtual="js/templateData.js" --></script>
+
+<!--#include virtual="../includes/_header.htm" -->
+<!--#include virtual="../includes/_top.htm" -->
+
+
+<div class="content documentation documentation--current">
+ <!--#include virtual="../includes/_nav.htm" -->
+ <div class="toc-handle-container">
+ <div class="toc-handle"><</div>
+ </div>
+ <div class="docs-nav">
+ <!--#include virtual="toc.html" -->
+ </div>
+ <div class="right">
+ <!--//#include virtual="../includes/_docs_banner.htm" -->
+
+ <h1>Documentation</h1>
+ <h3>Kafka 4.1 Documentation</h3>
+ Prior releases: <a href="/07/documentation.html">0.7.x</a>,
+ <a href="/08/documentation.html">0.8.0</a>,
+ <a href="/081/documentation.html">0.8.1.X</a>,
+ <a href="/082/documentation.html">0.8.2.X</a>,
+ <a href="/090/documentation.html">0.9.0.X</a>,
+ <a href="/0100/documentation.html">0.10.0.X</a>,
+ <a href="/0101/documentation.html">0.10.1.X</a>,
+ <a href="/0102/documentation.html">0.10.2.X</a>,
+ <a href="/0110/documentation.html">0.11.0.X</a>,
+ <a href="/10/documentation.html">1.0.X</a>,
+ <a href="/11/documentation.html">1.1.X</a>,
+ <a href="/20/documentation.html">2.0.X</a>,
+ <a href="/21/documentation.html">2.1.X</a>,
+ <a href="/22/documentation.html">2.2.X</a>,
+ <a href="/23/documentation.html">2.3.X</a>,
+ <a href="/24/documentation.html">2.4.X</a>,
+ <a href="/25/documentation.html">2.5.X</a>,
+ <a href="/26/documentation.html">2.6.X</a>,
+ <a href="/27/documentation.html">2.7.X</a>,
+ <a href="/28/documentation.html">2.8.X</a>,
+ <a href="/30/documentation.html">3.0.X</a>,
+ <a href="/31/documentation.html">3.1.X</a>,
+ <a href="/32/documentation.html">3.2.X</a>,
+ <a href="/33/documentation.html">3.3.X</a>,
+ <a href="/34/documentation.html">3.4.X</a>,
+ <a href="/35/documentation.html">3.5.X</a>,
+ <a href="/36/documentation.html">3.6.X</a>,
+ <a href="/37/documentation.html">3.7.X</a>,
+ <a href="/38/documentation.html">3.8.X</a>,
+ <a href="/39/documentation.html">3.9.X</a>.
+ <a href="/40/documentation.html">4.0.X</a>.
+
+ <h2 class="anchor-heading"><a id="gettingStarted" class="anchor-link"></a><a href="#gettingStarted">1. Getting Started</a></h2>
+ <h3 class="anchor-heading"><a id="introduction" class="anchor-link"></a><a href="#introduction">1.1 Introduction</a></h3>
+ <!--#include virtual="introduction.html" -->
+ <h3 class="anchor-heading"><a id="uses" class="anchor-link"></a><a href="#uses">1.2 Use Cases</a></h3>
+ <!--#include virtual="uses.html" -->
+ <h3 class="anchor-heading"><a id="quickstart" class="anchor-link"></a><a href="#quickstart">1.3 Quick Start</a></h3>
+ <!--#include virtual="quickstart.html" -->
+ <h3 class="anchor-heading"><a id="ecosystem" class="anchor-link"></a><a href="#ecosystem">1.4 Ecosystem</a></h3>
+ <!--#include virtual="ecosystem.html" -->
+ <h3 class="anchor-heading"><a id="upgrade" class="anchor-link"></a><a href="#upgrade">1.5 Upgrading From Previous Versions</a></h3>
+ <!--#include virtual="upgrade.html" -->
+ <h3 class="anchor-heading"><a id="zk2kraft-summary" class="anchor-link"></a><a href="#zk2kraft-summary">1.6 KRaft vs ZooKeeper</a></h3>
+ <!--#include virtual="zk2kraft-summary.html" -->
+ <h3 class="anchor-heading"><a id="compatibility-summary" class="anchor-link"></a><a href="#compatibility-summary">1.7 Compatibility</a></h3>
+ <!--#include virtual="compatibility-summary.html" -->
+ <h3 class="anchor-heading"><a id="docker" class="anchor-link"></a><a href="#docker">1.8 Docker</a></h3>
+ <!--#include virtual="docker.html" -->
+
+ <h2 class="anchor-heading"><a id="api" class="anchor-link"></a><a href="#api">2. APIs</a></h2>
+
+ <!--#include virtual="api.html" -->
+
+ <h2 class="anchor-heading"><a id="configuration" class="anchor-link"></a><a href="#configuration">3. Configuration</a></h2>
+
+ <!--#include virtual="configuration.html" -->
+
+ <h2 class="anchor-heading"><a id="design" class="anchor-link"></a><a href="#design">4. Design</a></h2>
+
+ <!--#include virtual="design.html" -->
+
+ <h2 class="anchor-heading"><a id="implementation" class="anchor-link"></a><a href="#implementation">5. Implementation</a></h2>
+
+ <!--#include virtual="implementation.html" -->
+
+ <h2 class="anchor-heading"><a id="operations" class="anchor-link"></a><a href="#operations">6. Operations</a></h2>
+
+ <!--#include virtual="ops.html" -->
+
+ <h2 class="anchor-heading"><a id="security" class="anchor-link"></a><a href="#security">7. Security</a></h2>
+ <!--#include virtual="security.html" -->
+
+ <h2 class="anchor-heading"><a id="connect" class="anchor-link"></a><a href="#connect">8. Kafka Connect</a></h2>
+ <!--#include virtual="connect.html" -->
+
+ <h2><a id="streams" href="#streams">9. Kafka Streams</a></h2>
+ <p>
+ Kafka Streams is a client library for processing and analyzing data stored in Kafka. It builds upon important stream processing concepts such as properly distinguishing between event time and processing time, windowing support, exactly-once processing semantics and simple yet efficient management of application state.
+ </p>
+ <p>
+ Kafka Streams has a <b>low barrier to entry</b>: You can quickly write and run a small-scale proof-of-concept on a single machine; and you only need to run additional instances of your application on multiple machines to scale up to high-volume production workloads. Kafka Streams transparently handles the load balancing of multiple instances of the same application by leveraging Kafka's parallelism model.
+ </p>
+
+ <p>To learn more about Kafka Streams, visit the <a href="/documentation/streams">Kafka Streams page</a>.</p>
+
+<!--#include virtual="../includes/_footer.htm" -->
+<!--#include virtual="../includes/_docs_footer.htm" -->
diff --git a/41/documentation/compatibility.html b/41/documentation/compatibility.html
new file mode 100644
index 000000000..e1b5134ea
--- /dev/null
+++ b/41/documentation/compatibility.html
@@ -0,0 +1,201 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!--#include virtual="../../includes/_header.htm" -->
+<!--#include virtual="../../includes/_top.htm" -->
+<div class="content">
+ <div class="p-compatibility">
+ <h1>Compatibility</h1>
+ With the release of Kafka 4.0, significant changes have been introduced that impact compatibility across various
+ components. To assist users in planning upgrades and ensuring seamless interoperability, a comprehensive
+ compatibility matrix has been prepared.
+ <h2 class="anchor-heading">JDK Compatibility Across Kafka Versions</h2>
+ <table>
+ <tr>
+ <th>Module</th>
+ <th>Kafka Version</th>
+ <th>Java 11</th>
+ <th>Java 17</th>
+ <th>Java 23</th>
+ </tr>
+ <tr>
+ <td>Clients</td>
+ <td>4.0.0</td>
+ <td>✅</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>Streams</td>
+ <td>4.0.0</td>
+ <td>✅</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>Connect</td>
+ <td>4.0.0</td>
+ <td>❌</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>Server</td>
+ <td>4.0.0</td>
+ <td>❌</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ </table>
+ <p><strong>Note: Java 8 is removed in Kafka 4.0 and is no longer supported.</strong></p>
+
+ <h2 class="anchor-heading">Server Compatibility</h2>
+ <table>
+ <tr>
+ <th>KRaft Cluster Version</th>
+ <th>Compatibility 4.0 Server (dynamic voter)</th>
+ <th>Compatibility 4.0 Server (static voter)</th>
+ </tr>
+ <tr>
+ <td>before 3.2.x</td>
+ <td>❌</td>
+ <td>❌</td>
+ </tr>
+ <tr>
+ <td>3.3.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.4.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.5.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.6.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.7.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.8.x</td>
+ <td>❌</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>3.9.x</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ <tr>
+ <td>4.0.x</td>
+ <td>✅</td>
+ <td>✅</td>
+ </tr>
+ </table>
+ <p><strong>Note: Can’t upgrade server from static voter to dynamic
+ voter, see <a href="https://issues.apache.org/jira/browse/KAFKA-16538">KAFKA-16538</a>.</strong></p>
+
+ <h4>Client/Broker Forward Compatibility</h4>
+ <table>
+ <tr>
+ <th>Kafka Version</th>
+ <th>Module</th>
+ <th>Compatibility with Kafka 4.0</th>
+ <th>Key Differences/Limitations</th>
+ </tr>
+ <tr>
+ <td rowspan="3">0.x, 1.x, 2.0</td>
+ <td>Client</td>
+ <td>❌ Not Compatible</td>
+ <td>Pre-0.10.x protocols are fully removed in Kafka 4.0 (<a
+ href="https://cwiki.apache.org/confluence/x/K5sODg">KIP-896</a>).
+ </td>
+ </tr>
+ <tr>
+ <td>Streams</td>
+ <td>❌ Not Compatible</td>
+ <td>Pre-0.10.x protocols are fully removed in Kafka 4.0 (<a
+ href="https://cwiki.apache.org/confluence/x/K5sODg">KIP-896</a>).
+ </td>
+ </tr>
+ <tr>
+ <td>Connect</td>
+ <td>❌ Not Compatible</td>
+ <td>Pre-0.10.x protocols are fully removed in Kafka 4.0 (<a
+ href="https://cwiki.apache.org/confluence/x/K5sODg">KIP-896</a>).
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="3">2.1 ~ 2.8</td>
+ <td>Client</td>
+ <td>⚠️ Partially Compatible</td>
+ <td>
+ More details in the <a href="/40/documentation.html#upgrade_400_notable_consumer">Consumer</a>,
+ <a href="/40/documentation.html#upgrade_400_notable_producer">Producer</a>, and
+ <a href="/40/documentation.html#upgrade_400_notable_admin_client">Admin Client</a> section.
+ </td>
+ </tr>
+ <tr>
+ <td>Streams</td>
+ <td>⚠️ Limited Compatibility</td>
+ <td>
+ More details in the <a href="/40/documentation.html#upgrade_400_notable_kafka_streams">Kafka Streams</a> section.
+ </td>
+ </tr>
+ <tr>
+ <td>Connect</td>
+ <td>⚠️ Limited Compatibility</td>
+ <td>
+ More details in the <a href="/40/documentation.html#upgrade_400_notable_connect">Connect</a> section.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="3">3.x</td>
+ <td>Client</td>
+ <td>✅ Fully Compatible</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Streams</td>
+ <td>✅ Fully Compatible</td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>Connect</td>
+ <td>✅ Fully Compatible</td>
+ <td></td>
+ </tr>
+ </table>
+ <p>
+ Note: Starting with Kafka 4.0, the <code>--zookeeper</code> option in AdminClient commands has been removed. Users must
+ use the <code>--bootstrap-server</code> option to interact with the Kafka cluster. This change aligns with the transition
+ to KRaft mode.
+ </p>
+
+ </div>
+ <!--#include virtual="../../includes/_footer.htm" -->
+</div>
\ No newline at end of file
diff --git a/41/documentation/index.html b/41/documentation/index.html
new file mode 100644
index 000000000..1d7507f30
--- /dev/null
+++ b/41/documentation/index.html
@@ -0,0 +1,18 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!--#include virtual="../documentation.html" -->
\ No newline at end of file
diff --git a/41/documentation/streams/architecture.html b/41/documentation/streams/architecture.html
new file mode 100644
index 000000000..ad7b323d0
--- /dev/null
+++ b/41/documentation/streams/architecture.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/architecture.html" -->
diff --git a/41/documentation/streams/core-concepts.html b/41/documentation/streams/core-concepts.html
new file mode 100644
index 000000000..d699b7950
--- /dev/null
+++ b/41/documentation/streams/core-concepts.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/core-concepts.html" -->
diff --git a/41/documentation/streams/developer-guide/app-reset-tool.html b/41/documentation/streams/developer-guide/app-reset-tool.html
new file mode 100644
index 000000000..64a43aa0c
--- /dev/null
+++ b/41/documentation/streams/developer-guide/app-reset-tool.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/app-reset-tool.html" -->
diff --git a/41/documentation/streams/developer-guide/config-streams.html b/41/documentation/streams/developer-guide/config-streams.html
new file mode 100644
index 000000000..979f66d68
--- /dev/null
+++ b/41/documentation/streams/developer-guide/config-streams.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/config-streams.html" -->
diff --git a/41/documentation/streams/developer-guide/datatypes.html b/41/documentation/streams/developer-guide/datatypes.html
new file mode 100644
index 000000000..98dd3a1c7
--- /dev/null
+++ b/41/documentation/streams/developer-guide/datatypes.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/datatypes.html" -->
diff --git a/41/documentation/streams/developer-guide/dsl-api.html b/41/documentation/streams/developer-guide/dsl-api.html
new file mode 100644
index 000000000..1bbc06d5d
--- /dev/null
+++ b/41/documentation/streams/developer-guide/dsl-api.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/dsl-api.html" -->
diff --git a/41/documentation/streams/developer-guide/dsl-topology-naming.html b/41/documentation/streams/developer-guide/dsl-topology-naming.html
new file mode 100644
index 000000000..9f42a04ac
--- /dev/null
+++ b/41/documentation/streams/developer-guide/dsl-topology-naming.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/dsl-topology-naming.html" -->
diff --git a/41/documentation/streams/developer-guide/index.html b/41/documentation/streams/developer-guide/index.html
new file mode 100644
index 000000000..3a6124776
--- /dev/null
+++ b/41/documentation/streams/developer-guide/index.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/index.html" -->
diff --git a/41/documentation/streams/developer-guide/interactive-queries.html b/41/documentation/streams/developer-guide/interactive-queries.html
new file mode 100644
index 000000000..05060121e
--- /dev/null
+++ b/41/documentation/streams/developer-guide/interactive-queries.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/interactive-queries.html" -->
diff --git a/41/documentation/streams/developer-guide/manage-topics.html b/41/documentation/streams/developer-guide/manage-topics.html
new file mode 100644
index 000000000..f4225541e
--- /dev/null
+++ b/41/documentation/streams/developer-guide/manage-topics.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/manage-topics.html" -->
diff --git a/41/documentation/streams/developer-guide/memory-mgmt.html b/41/documentation/streams/developer-guide/memory-mgmt.html
new file mode 100644
index 000000000..024e1374c
--- /dev/null
+++ b/41/documentation/streams/developer-guide/memory-mgmt.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/memory-mgmt.html" -->
diff --git a/41/documentation/streams/developer-guide/processor-api.html b/41/documentation/streams/developer-guide/processor-api.html
new file mode 100644
index 000000000..9e9ab91f0
--- /dev/null
+++ b/41/documentation/streams/developer-guide/processor-api.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/processor-api.html" -->
diff --git a/41/documentation/streams/developer-guide/running-app.html b/41/documentation/streams/developer-guide/running-app.html
new file mode 100644
index 000000000..05d5f0b1f
--- /dev/null
+++ b/41/documentation/streams/developer-guide/running-app.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/running-app.html" -->
diff --git a/41/documentation/streams/developer-guide/security.html b/41/documentation/streams/developer-guide/security.html
new file mode 100644
index 000000000..5d6e5f0d9
--- /dev/null
+++ b/41/documentation/streams/developer-guide/security.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/security.html" -->
diff --git a/41/documentation/streams/developer-guide/testing.html b/41/documentation/streams/developer-guide/testing.html
new file mode 100644
index 000000000..4753e66ad
--- /dev/null
+++ b/41/documentation/streams/developer-guide/testing.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/testing.html" -->
diff --git a/41/documentation/streams/developer-guide/write-streams.html b/41/documentation/streams/developer-guide/write-streams.html
new file mode 100644
index 000000000..976c6fe14
--- /dev/null
+++ b/41/documentation/streams/developer-guide/write-streams.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../../streams/developer-guide/write-streams.html" -->
diff --git a/41/documentation/streams/index.html b/41/documentation/streams/index.html
new file mode 100644
index 000000000..5ff3b3b6f
--- /dev/null
+++ b/41/documentation/streams/index.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/index.html" -->
diff --git a/41/documentation/streams/quickstart.html b/41/documentation/streams/quickstart.html
new file mode 100644
index 000000000..efb0234e2
--- /dev/null
+++ b/41/documentation/streams/quickstart.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/quickstart.html" -->
diff --git a/41/documentation/streams/tutorial.html b/41/documentation/streams/tutorial.html
new file mode 100644
index 000000000..e2cf4016e
--- /dev/null
+++ b/41/documentation/streams/tutorial.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/tutorial.html" -->
diff --git a/41/documentation/streams/upgrade-guide.html b/41/documentation/streams/upgrade-guide.html
new file mode 100644
index 000000000..b1b32007e
--- /dev/null
+++ b/41/documentation/streams/upgrade-guide.html
@@ -0,0 +1,19 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!-- should always link the latest release's documentation -->
+<!--#include virtual="../../streams/upgrade-guide.html" -->
diff --git a/41/documentation/zk2kraft.html b/41/documentation/zk2kraft.html
new file mode 100644
index 000000000..69e322bb0
--- /dev/null
+++ b/41/documentation/zk2kraft.html
@@ -0,0 +1,320 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!--#include virtual="../../includes/_header.htm" -->
+<!--#include virtual="../../includes/_top.htm" -->
+<div class="content">
+<div class="p-zk2kraft">
+ <h1>Differences Between KRaft mode and ZooKeeper mode</h1>
+ <h2 class="anchor-heading">Removed ZooKeeper Features</h2>
+ <p>
+ This section documents differences in behavior between KRaft mode and ZooKeeper mode.
+ Specifically, several configurations, metrics and features have changed or are no longer required in KRaft mode.
+ To migrate an existing cluster from ZooKeeper mode to KRaft mode, please refer to the
+ <a href="/39/documentation.html#kraft_zk_migration">ZooKeeper to KRaft Migration</a> section.
+ </p>
+ <h3 class="anchor-heading">Configurations</h3>
+ <ul>
+ <li>
+ <p>
+ Removed password encoder-related configurations. These configurations were used in
+ ZooKeeper mode to define the key and backup key for encrypting sensitive data (e.g., passwords),
+ specify the algorithm and key generation method for password encryption (e.g., AES, RSA), and control
+ the key length and encryption strength.
+ </p>
+ <ul>
+ <li><code>password.encoder.secret</code></li>
+ <li><code>password.encoder.old.secret</code></li>
+ <li><code>password.encoder.keyfactory.algorithm</code></li>
+ <li><code>password.encoder.cipher.algorithm</code></li>
+ <li><code>password.encoder.key.length</code></li>
+ <li><code>password.encoder.iterations</code></li>
+ </ul>
+ <p>
+ In KRaft mode, Kafka stores sensitive data in records, and the data is not encrypted in Kafka.
+ </p>
+ </li>
+ <li>
+ <p>
+ Removed <code>control.plane.listener.name</code>. Kafka relies on ZooKeeper to manage metadata, but some
+ internal operations (e.g., communication between controllers (a.k.a., broker controller) and brokers)
+ still require Kafka’s internal control plane for coordination.
+ </p>
+ <p>
+ In KRaft mode, Kafka eliminates its dependency on ZooKeeper, and the control plane functionality is
+ fully integrated into Kafka itself. The process roles are clearly separated: brokers handle data-related
+ requests, while the controllers (a.k.a., quorum controller) manages metadata-related requests. The controllers
+ use the Raft protocol for internal communication, which operates differently from the ZooKeeper model. Use the
+ following parameters to configure the control plane listener:
+ </p>
+ <ul>
+ <li><code>controller.listener.names</code></li>
+ <li><code>listeners</code></li>
+ <li><code>listener.security.protocol.map</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed graceful broker shutdowns-related configurations. These configurations were used in ZooKeeper mode
+ to define the maximum number of retries and the retry backoff time for controlled shutdowns. It can
+ reduce the risk of unplanned leader changes and data inconsistencies.
+ </p>
+ <ul>
+ <li><code>controlled.shutdown.max.retries</code></li>
+ <li><code>controlled.shutdown.retry.backoff.ms</code></li>
+ </ul>
+ <p>
+ In KRaft mode, Kafka uses the Raft protocol to manage metadata. The broker shutdown process differs from
+ ZooKeeper mode as it is managed by the quorum-based controller. The shutdown process is more reliable
+ and efficient due to automated leader transfers and metadata updates handled by the controller.
+ </p>
+ </li>
+ <li>
+ <p>
+ Removed the broker id generation-related configurations. These configurations were used in ZooKeeper mode
+ to specify the broker id auto generation and control the broker id generation process.
+ </p>
+ <ul>
+ <li><code>reserved.broker.max.id</code></li>
+ <li><code>broker.id.generation.enable</code></li>
+ </ul>
+ <p>
+ Kafka uses the node id in KRaft mode to identify servers.
+ </p>
+ <ul>
+ <li><code>node.id</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed broker protocol version-related configurations. These configurations were used in ZooKeeper mode to define communication protocol version between brokers.
+ In KRaft mode, Kafka uses <code>metadata.version</code> to control the feature level of the cluster, which can be managed using <code>bin/kafka-features.sh</code>.
+ </p>
+ <ul>
+ <li><code>inter.broker.protocol.version</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed dynamic configurations which relied on ZooKeeper. In KRaft mode, to change these configurations,
+ you need to restart the broker/controller.
+ </p>
+ <ul>
+ <li><code>advertised.listeners</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed the leader imbalance configuration used only in ZooKeeper. <code>leader.imbalance.per.broker.percentage</code>
+ was used to limit the preferred leader election frequency in ZooKeeper.
+ </p>
+ <ul>
+ <li><code>leader.imbalance.per.broker.percentage</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed ZooKeeper related configurations.
+ </p>
+ <ul>
+ <li><code>zookeeper.connect</code></li>
+ <li><code>zookeeper.session.timeout.ms</code></li>
+ <li><code>zookeeper.connection.timeout.ms</code></li>
+ <li><code>zookeeper.set.acl</code></li>
+ <li><code>zookeeper.max.in.flight.requests</code></li>
+ <li><code>zookeeper.ssl.client.enable</code></li>
+ <li><code>zookeeper.clientCnxnSocket</code></li>
+ <li><code>zookeeper.ssl.keystore.location</code></li>
+ <li><code>zookeeper.ssl.keystore.password</code></li>
+ <li><code>zookeeper.ssl.keystore.type</code></li>
+ <li><code>zookeeper.ssl.truststore.location</code></li>
+ <li><code>zookeeper.ssl.truststore.password</code></li>
+ <li><code>zookeeper.ssl.truststore.type</code></li>
+ <li><code>zookeeper.ssl.protocol</code></li>
+ <li><code>zookeeper.ssl.enabled.protocols</code></li>
+ <li><code>zookeeper.ssl.cipher.suites</code></li>
+ <li><code>zookeeper.ssl.endpoint.identification.algorithm</code></li>
+ <li><code>zookeeper.ssl.crl.enable</code></li>
+ <li><code>zookeeper.ssl.ocsp.enable</code></li>
+ </ul>
+ </li>
+ </ul>
+ <h3 class="anchor-heading">Dynamic Log Levels</h3>
+ <ul>
+ <li>
+ <p>
+ The dynamic log levels feature allows you to change the log4j settings of a running broker or controller process without restarting it. The command-line syntax for setting dynamic log levels on brokers has not changed in KRaft mode. Here is an example of setting the log level on a broker:<br/>
+ <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+ --entity-type broker-loggers \
+ --entity-name 1 \
+ --alter \
+ --add-config org.apache.kafka.raft.KafkaNetworkChannel=TRACE
+ </code></pre>
+ </p>
+ </li>
+ <li>
+ <p>
+ When setting dynamic log levels on the controllers, the <code>--bootstrap-controller</code> flag must be used. Here is an example of setting the log level ona controller:<br/>
+ <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-controller localhost:9093 \
+ --entity-type broker-loggers \
+ --entity-name 1 \
+ --alter \
+ --add-config org.apache.kafka.raft.KafkaNetworkChannel=TRACE
+ </code></pre><br/>
+ Note that the entity-type must be specified as <code>broker-loggers</code>, even though we are changing a controller's log level rather than a broker's log level.
+ </p>
+ </li>
+ <li>
+ <p>
+ When changing the log level of a combined node, which has both broker and controller roles, either --bootstrap-servers or --bootstrap-controllers may be used. Combined nodes have only a single set of log levels; there are not different log levels for the broker and controller parts of the process.
+ </p>
+ </li>
+ </ul>
+ <h3 class="anchor-heading">Dynamic Controller Configurations</h3>
+ <ul>
+ <li>
+ <p>
+ Some Kafka configurations can be changed dynamically, without restarting the process. The command-line syntax for setting dynamic log levels on brokers has not changed in KRaft mode. Here is an example of setting the number of IO threads on a broker:<br/>
+ <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+ --entity-type brokers \
+ --entity-name 1 \
+ --alter \
+ --add-config num.io.threads=5
+ </code></pre>
+ </p>
+ </li>
+ <li>
+ <p>
+ Controllers will apply all applicable cluster-level dynamic configurations. For example, the following command-line will change the <code>max.connections</code> setting on all of the brokers and all of the controllers in the cluster:<br/>
+ <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+ --entity-type brokers \
+ --entity-default \
+ --alter \
+ --add-config max.connections=10000
+ </code></pre><br/>
+ It is not currently possible to apply a dynamic configuration on only a single controller.
+ </p>
+ </li>
+ </ul>
+ <h2 class="anchor-heading">Metrics</h2>
+ <ul>
+ <li>
+ <p>
+ Removed the following metrics related to ZooKeeper.
+ <code>ControlPlaneNetworkProcessorAvgIdlePercent</code>
+ is to monitor the average fraction of time the network processors are idle. The other <code>ControlPlaneExpiredConnectionsKilledCount</code>
+ is to monitor the total number of connections disconnected, across all processors.
+ </p>
+ <ul>
+ <li><code>ControlPlaneNetworkProcessorAvgIdlePercent</code></li>
+ <li><code>ControlPlaneExpiredConnectionsKilledCount</code></li>
+ </ul>
+ <p>
+ In KRaft mode, Kafka also provides metrics to monitor the network processors and expired connections.
+ Use the following metrics to monitor the network processors and expired connections:
+ </p>
+ <ul>
+ <li><code>NetworkProcessorAvgIdlePercent</code></li>
+ <li><code>ExpiredConnectionsKilledCount</code></li>
+ </ul>
+ </li>
+ <li>
+ <p>
+ Removed the metrics which are only used in ZooKeeper mode.
+ </p>
+ <ul>
+ <li><code>kafka.controller:type=ControllerChannelManager,name=QueueSize</code></li>
+ <li><code>kafka.controller:type=ControllerChannelManager,name=RequestRateAndQueueTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerEventManager,name=EventQueueSize</code></li>
+ <li><code>kafka.controller:type=ControllerEventManager,name=EventQueueTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=AutoLeaderBalanceRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=ControlledShutdownRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=ControllerChangeRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=ControllerShutdownRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=IdleRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=IsrChangeRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=LeaderAndIsrResponseReceivedRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=LeaderElectionRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=ListPartitionReassignmentRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=LogDirChangeRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=ManualLeaderBalanceRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=MigratingZkBrokerCount</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=PartitionReassignmentRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=TopicChangeRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=TopicDeletionRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=TopicsIneligibleToDeleteCount</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=TopicUncleanLeaderElectionEnableRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=UncleanLeaderElectionEnableRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=UncleanLeaderElectionsPerSec</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=UpdateFeaturesRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=ControllerStats,name=UpdateMetadataResponseReceivedRateAndTimeMs</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ActiveBrokerCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ActiveControllerCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ControllerState</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=FencedBrokerCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=GlobalPartitionCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=GlobalTopicCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=OfflinePartitionsCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=PreferredReplicaImbalanceCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ReplicasIneligibleToDeleteCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ReplicasToDeleteCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=TopicsToDeleteCount</code></li>
+ <li><code>kafka.controller:type=KafkaController,name=ZkMigrationState</code></li>
+ <li><code>kafka.server:type=DelayedOperationPurgatory,name=PurgatorySize,delayedOperation=ElectLeader</code></li>
+ <li><code>kafka.server:type=DelayedOperationPurgatory,name=PurgatorySize,delayedOperation=topic</code></li>
+ <li><code>kafka.server:type=DelayedOperationPurgatory,name=NumDelayedOperations,delayedOperation=ElectLeader</code></li>
+ <li><code>kafka.server:type=DelayedOperationPurgatory,name=NumDelayedOperations,delayedOperation=topic</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=SessionState</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperAuthFailuresPerSec</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperDisconnectsPerSec</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperExpiresPerSec</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperReadOnlyConnectsPerSec</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperSaslAuthenticationsPerSec</code></li>
+ <li><code>kafka.server:type=SessionExpireListener,name=ZooKeeperSyncConnectsPerSec</code></li>
+ <li><code>kafka.server:type=ZooKeeperClientMetrics,name=ZooKeeperRequestLatencyMs</code></li>
+ </ul>
+ </li>
+ </ul>
+ <h2 class="anchor-heading">Behavioral Change Reference</h2>
+ <p>
+ This document catalogs the functional and operational differences between ZooKeeper mode and KRaft mode.
+ </p>
+ <ul>
+ <li>
+ <strong>Configuration Value Size Limitation</strong>: KRaft mode restricts configuration values to a maximum size of <code>Short.MAX_VALUE</code>,
+ which prevents using the append operation to create larger configuration values.
+ </li>
+ <li>
+ <strong>Policy Class Deployment</strong>:
+ In KRaft mode, the <code>CreateTopicPolicy</code> and <code>AlterConfigPolicy</code> plugins run on the controller instead of the broker.
+ This requires users to deploy the policy class JAR files on the controller and configure the parameters
+ (<code>create.topic.policy.class.name</code> and <code>alter.config.policy.class.name</code>) on the controller.
+ <p>Note: If migrating from ZooKeeper mode, ensure policy JARs are moved from brokers to controllers.</p>
+ </li>
+ <li>
+ <strong>Custom implementations of <code>KafkaPrincipalBuilder</code></strong>:
+ In KRaft mode, custom implementations of <code>KafkaPrincipalBuilder</code> must also implement <code>KafkaPrincipalSerde</code>; otherwise brokers will not be able to
+ forward requests to the controller.
+ </li>
+ </ul>
+</div>
+<!--#include virtual="../../includes/_footer.htm" -->
+</div>
diff --git a/41/ecosystem.html b/41/ecosystem.html
new file mode 100644
index 000000000..a198e2efd
--- /dev/null
+++ b/41/ecosystem.html
@@ -0,0 +1,18 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+There are a plethora of tools that integrate with Kafka outside the main distribution. The <a href="https://cwiki.apache.org/confluence/x/Ri3VAQ"> ecosystem page</a> lists many of these, including stream processing systems, Hadoop integration, monitoring, and deployment tools.
diff --git a/41/generated/admin_client_config.html b/41/generated/admin_client_config.html
new file mode 100644
index 000000000..d09ea7b11
--- /dev/null
+++ b/41/generated/admin_client_config.html
@@ -0,0 +1,903 @@
+<ul class="config-list">
+<li>
+<h4><a id="bootstrap.controllers"></a><a id="adminclientconfigs_bootstrap.controllers" href="#adminclientconfigs_bootstrap.controllers">bootstrap.controllers</a></h4>
+<p>A list of host/port pairs to use for establishing the initial connection to the KRaft controller quorum. This list should be in the form <code>host1:port1,host2:port2,...</code>.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="bootstrap.servers"></a><a id="adminclientconfigs_bootstrap.servers" href="#adminclientconfigs_bootstrap.servers">bootstrap.servers</a></h4>
+<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.key.password"></a><a id="adminclientconfigs_ssl.key.password" href="#adminclientconfigs_ssl.key.password">ssl.key.password</a></h4>
+<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.certificate.chain"></a><a id="adminclientconfigs_ssl.keystore.certificate.chain" href="#adminclientconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
+<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.key"></a><a id="adminclientconfigs_ssl.keystore.key" href="#adminclientconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
+<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.location"></a><a id="adminclientconfigs_ssl.keystore.location" href="#adminclientconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
+<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.password"></a><a id="adminclientconfigs_ssl.keystore.password" href="#adminclientconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
+<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.certificates"></a><a id="adminclientconfigs_ssl.truststore.certificates" href="#adminclientconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
+<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.location"></a><a id="adminclientconfigs_ssl.truststore.location" href="#adminclientconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
+<p>The location of the trust store file.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.password"></a><a id="adminclientconfigs_ssl.truststore.password" href="#adminclientconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
+<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.dns.lookup"></a><a id="adminclientconfigs_client.dns.lookup" href="#adminclientconfigs_client.dns.lookup">client.dns.lookup</a></h4>
+<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
+<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.id"></a><a id="adminclientconfigs_client.id" href="#adminclientconfigs_client.id">client.id</a></h4>
+<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="connections.max.idle.ms"></a><a id="adminclientconfigs_connections.max.idle.ms" href="#adminclientconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
+<p>Close idle connections after the number of milliseconds specified by this config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="default.api.timeout.ms"></a><a id="adminclientconfigs_default.api.timeout.ms" href="#adminclientconfigs_default.api.timeout.ms">default.api.timeout.ms</a></h4>
+<p>Specifies the timeout (in milliseconds) for client APIs. This configuration is used as the default timeout for all client operations that do not specify a <code>timeout</code> parameter.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="receive.buffer.bytes"></a><a id="adminclientconfigs_receive.buffer.bytes" href="#adminclientconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
+<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>65536 (64 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="request.timeout.ms"></a><a id="adminclientconfigs_request.timeout.ms" href="#adminclientconfigs_request.timeout.ms">request.timeout.ms</a></h4>
+<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.client.callback.handler.class"></a><a id="adminclientconfigs_sasl.client.callback.handler.class" href="#adminclientconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.jaas.config"></a><a id="adminclientconfigs_sasl.jaas.config" href="#adminclientconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
+<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.service.name"></a><a id="adminclientconfigs_sasl.kerberos.service.name" href="#adminclientconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
+<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.callback.handler.class"></a><a id="adminclientconfigs_sasl.login.callback.handler.class" href="#adminclientconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.class"></a><a id="adminclientconfigs_sasl.login.class" href="#adminclientconfigs_sasl.login.class">sasl.login.class</a></h4>
+<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.mechanism"></a><a id="adminclientconfigs_sasl.mechanism" href="#adminclientconfigs_sasl.mechanism">sasl.mechanism</a></h4>
+<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>GSSAPI</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.algorithm" href="#adminclientconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
+<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>RS256</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.aud" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
+<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.iss" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
+<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
+<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.sub" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
+<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
+<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.private.key.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
+<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#adminclientconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
+<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.template.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
+<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="adminclientconfigs_sasl.oauthbearer.client.credentials.client.id" href="#adminclientconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
+<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="adminclientconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#adminclientconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
+<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
+<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="adminclientconfigs_sasl.oauthbearer.jwt.retriever.class" href="#adminclientconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="adminclientconfigs_sasl.oauthbearer.jwt.validator.class" href="#adminclientconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.scope"></a><a id="adminclientconfigs_sasl.oauthbearer.scope" href="#adminclientconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
+<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="adminclientconfigs_sasl.oauthbearer.token.endpoint.url" href="#adminclientconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
+<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="security.protocol"></a><a id="adminclientconfigs_security.protocol" href="#adminclientconfigs_security.protocol">security.protocol</a></h4>
+<p>Protocol used to communicate with brokers.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>PLAINTEXT</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="send.buffer.bytes"></a><a id="adminclientconfigs_send.buffer.bytes" href="#adminclientconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
+<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="adminclientconfigs_socket.connection.setup.timeout.max.ms" href="#adminclientconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
+<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.ms"></a><a id="adminclientconfigs_socket.connection.setup.timeout.ms" href="#adminclientconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
+<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.enabled.protocols"></a><a id="adminclientconfigs_ssl.enabled.protocols" href="#adminclientconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
+<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. Also see the config documentation for `ssl.protocol` to understand how it can impact the TLS version negotiation behavior.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.type"></a><a id="adminclientconfigs_ssl.keystore.type" href="#adminclientconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
+<p>The file format of the key store file. This is optional for client. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.protocol"></a><a id="adminclientconfigs_ssl.protocol" href="#adminclientconfigs_ssl.protocol">ssl.protocol</a></h4>
+<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in `ssl.enabled [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.provider"></a><a id="adminclientconfigs_ssl.provider" href="#adminclientconfigs_ssl.provider">ssl.provider</a></h4>
+<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.type"></a><a id="adminclientconfigs_ssl.truststore.type" href="#adminclientconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
+<p>The file format of the trust store file. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="enable.metrics.push"></a><a id="adminclientconfigs_enable.metrics.push" href="#adminclientconfigs_enable.metrics.push">enable.metrics.push</a></h4>
+<p>Whether to enable pushing of client metrics to the cluster, if the cluster has a client metrics subscription which matches this client.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.max.age.ms"></a><a id="adminclientconfigs_metadata.max.age.ms" href="#adminclientconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
+<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="adminclientconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#adminclientconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
+<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.strategy"></a><a id="adminclientconfigs_metadata.recovery.strategy" href="#adminclientconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
+<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>rebootstrap</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metric.reporters"></a><a id="adminclientconfigs_metric.reporters" href="#adminclientconfigs_metric.reporters">metric.reporters</a></h4>
+<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.num.samples"></a><a id="adminclientconfigs_metrics.num.samples" href="#adminclientconfigs_metrics.num.samples">metrics.num.samples</a></h4>
+<p>The number of samples maintained to compute metrics.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>2</td></tr>
+<tr><th>Valid Values:</th><td>[1,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.recording.level"></a><a id="adminclientconfigs_metrics.recording.level" href="#adminclientconfigs_metrics.recording.level">metrics.recording.level</a></h4>
+<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>INFO</td></tr>
+<tr><th>Valid Values:</th><td>[INFO, DEBUG, TRACE]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.sample.window.ms"></a><a id="adminclientconfigs_metrics.sample.window.ms" href="#adminclientconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
+<p>The window of time a metrics sample is computed over.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.max.ms"></a><a id="adminclientconfigs_reconnect.backoff.max.ms" href="#adminclientconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.ms"></a><a id="adminclientconfigs_reconnect.backoff.ms" href="#adminclientconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
+<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>50</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retries"></a><a id="adminclientconfigs_retries" href="#adminclientconfigs_retries">retries</a></h4>
+<p>It is recommended to set the value to either <code>MAX_VALUE</code> or zero, and use corresponding timeout parameters to control how long a client should retry a request. Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error. Setting a value of zero will lead to transient errors not being retried, and they will be propagated to the application to be handled.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>2147483647</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.max.ms"></a><a id="adminclientconfigs_retry.backoff.max.ms" href="#adminclientconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.ms"></a><a id="adminclientconfigs_retry.backoff.ms" href="#adminclientconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
+<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="adminclientconfigs_sasl.kerberos.kinit.cmd" href="#adminclientconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
+<p>Kerberos kinit command path.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="adminclientconfigs_sasl.kerberos.min.time.before.relogin" href="#adminclientconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
+<p>Login thread sleep time between refresh attempts.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>60000</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="adminclientconfigs_sasl.kerberos.ticket.renew.jitter" href="#adminclientconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
+<p>Percentage of random jitter added to the renewal time.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.05</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="adminclientconfigs_sasl.kerberos.ticket.renew.window.factor" href="#adminclientconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
+<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.connect.timeout.ms"></a><a id="adminclientconfigs_sasl.login.connect.timeout.ms" href="#adminclientconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.read.timeout.ms"></a><a id="adminclientconfigs_sasl.login.read.timeout.ms" href="#adminclientconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="adminclientconfigs_sasl.login.refresh.buffer.seconds" href="#adminclientconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
+<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>300</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="adminclientconfigs_sasl.login.refresh.min.period.seconds" href="#adminclientconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
+<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>60</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.window.factor"></a><a id="adminclientconfigs_sasl.login.refresh.window.factor" href="#adminclientconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
+<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.window.jitter"></a><a id="adminclientconfigs_sasl.login.refresh.window.jitter" href="#adminclientconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
+<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.05</td></tr>
+<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="adminclientconfigs_sasl.login.retry.backoff.max.ms" href="#adminclientconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
+<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.retry.backoff.ms"></a><a id="adminclientconfigs_sasl.login.retry.backoff.ms" href="#adminclientconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
+<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
+<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>300</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
+<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>60</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.clock.skew.seconds" href="#adminclientconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
+<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>30</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="adminclientconfigs_sasl.oauthbearer.expected.audience" href="#adminclientconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
+<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="adminclientconfigs_sasl.oauthbearer.expected.issuer" href="#adminclientconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
+<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="adminclientconfigs_sasl.oauthbearer.header.urlencode" href="#adminclientconfigs_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
+<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
+<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
+<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
+<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="adminclientconfigs_sasl.oauthbearer.scope.claim.name" href="#adminclientconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
+<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>scope</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="adminclientconfigs_sasl.oauthbearer.sub.claim.name" href="#adminclientconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
+<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>sub</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="security.providers"></a><a id="adminclientconfigs_security.providers" href="#adminclientconfigs_security.providers">security.providers</a></h4>
+<p>A list of configurable creator classes each returning a provider implementing security algorithms. These classes should implement the <code>org.apache.kafka.common.security.auth.SecurityProviderCreator</code> interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.cipher.suites"></a><a id="adminclientconfigs_ssl.cipher.suites" href="#adminclientconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
+<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="adminclientconfigs_ssl.endpoint.identification.algorithm" href="#adminclientconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
+<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>https</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.engine.factory.class"></a><a id="adminclientconfigs_ssl.engine.factory.class" href="#adminclientconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
+<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keymanager.algorithm"></a><a id="adminclientconfigs_ssl.keymanager.algorithm" href="#adminclientconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
+<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>SunX509</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.secure.random.implementation"></a><a id="adminclientconfigs_ssl.secure.random.implementation" href="#adminclientconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
+<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.trustmanager.algorithm"></a><a id="adminclientconfigs_ssl.trustmanager.algorithm" href="#adminclientconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
+<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>PKIX</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+</ul>
+
diff --git a/41/generated/connect_config.html b/41/generated/connect_config.html
new file mode 100644
index 000000000..1dd2007bb
--- /dev/null
+++ b/41/generated/connect_config.html
@@ -0,0 +1,1333 @@
+<ul class="config-list">
+<li>
+<h4><a id="config.storage.topic"></a><a id="connectconfigs_config.storage.topic" href="#connectconfigs_config.storage.topic">config.storage.topic</a></h4>
+<p>The name of the Kafka topic where connector configurations are stored</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="group.id"></a><a id="connectconfigs_group.id" href="#connectconfigs_group.id">group.id</a></h4>
+<p>A unique string that identifies the Connect cluster group this worker belongs to.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="key.converter"></a><a id="connectconfigs_key.converter" href="#connectconfigs_key.converter">key.converter</a></h4>
+<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="offset.storage.topic"></a><a id="connectconfigs_offset.storage.topic" href="#connectconfigs_offset.storage.topic">offset.storage.topic</a></h4>
+<p>The name of the Kafka topic where source connector offsets are stored</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="status.storage.topic"></a><a id="connectconfigs_status.storage.topic" href="#connectconfigs_status.storage.topic">status.storage.topic</a></h4>
+<p>The name of the Kafka topic where connector and task status are stored</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="value.converter"></a><a id="connectconfigs_value.converter" href="#connectconfigs_value.converter">value.converter</a></h4>
+<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="bootstrap.servers"></a><a id="connectconfigs_bootstrap.servers" href="#connectconfigs_bootstrap.servers">bootstrap.servers</a></h4>
+<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>localhost:9092</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="exactly.once.source.support"></a><a id="connectconfigs_exactly.once.source.support" href="#connectconfigs_exactly.once.source.support">exactly.once.source.support</a></h4>
+<p>Whether to enable exactly-once support for source connectors in the cluster by using transactions to write source records and their source offsets, and by proactively fencing out old task generations before bringing up new ones.<br>To enable exactly-once source support on a new cluster, set this property to 'enabled'. To enable support on an existing cluster, first set to 'preparing' on every worker in the cluster, then set to 'enabled'. A rolling upgrade may be used for both changes. [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>disabled</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [DISABLED, ENABLED, PREPARING]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="heartbeat.interval.ms"></a><a id="connectconfigs_heartbeat.interval.ms" href="#connectconfigs_heartbeat.interval.ms">heartbeat.interval.ms</a></h4>
+<p>The expected time between heartbeats to the group coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the worker's session stays active and to facilitate rebalancing when new members join or leave the group. The value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can be adjusted even lower to control the expected time for normal rebalances.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="rebalance.timeout.ms"></a><a id="connectconfigs_rebalance.timeout.ms" href="#connectconfigs_rebalance.timeout.ms">rebalance.timeout.ms</a></h4>
+<p>The maximum allowed time for each worker to join the group once a rebalance has begun. This is basically a limit on the amount of time needed for all tasks to flush any pending data and commit offsets. If the timeout is exceeded, then the worker will be removed from the group, which will cause offset commit failures.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="session.timeout.ms"></a><a id="connectconfigs_session.timeout.ms" href="#connectconfigs_session.timeout.ms">session.timeout.ms</a></h4>
+<p>The timeout used to detect worker failures. The worker sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove the worker from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min.session.timeout.ms</code> and <code>group.max.session.timeout.ms</code>.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.key.password"></a><a id="connectconfigs_ssl.key.password" href="#connectconfigs_ssl.key.password">ssl.key.password</a></h4>
+<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.certificate.chain"></a><a id="connectconfigs_ssl.keystore.certificate.chain" href="#connectconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
+<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.key"></a><a id="connectconfigs_ssl.keystore.key" href="#connectconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
+<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.location"></a><a id="connectconfigs_ssl.keystore.location" href="#connectconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
+<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.password"></a><a id="connectconfigs_ssl.keystore.password" href="#connectconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
+<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.certificates"></a><a id="connectconfigs_ssl.truststore.certificates" href="#connectconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
+<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.location"></a><a id="connectconfigs_ssl.truststore.location" href="#connectconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
+<p>The location of the trust store file.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.password"></a><a id="connectconfigs_ssl.truststore.password" href="#connectconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
+<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.dns.lookup"></a><a id="connectconfigs_client.dns.lookup" href="#connectconfigs_client.dns.lookup">client.dns.lookup</a></h4>
+<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
+<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="connections.max.idle.ms"></a><a id="connectconfigs_connections.max.idle.ms" href="#connectconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
+<p>Close idle connections after the number of milliseconds specified by this config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>540000 (9 minutes)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="connector.client.config.override.policy"></a><a id="connectconfigs_connector.client.config.override.policy" href="#connectconfigs_connector.client.config.override.policy">connector.client.config.override.policy</a></h4>
+<p>Class name or alias of implementation of <code>ConnectorClientConfigOverridePolicy</code>. Defines what client configurations can be overridden by the connector. The default implementation is `All`, meaning connector configurations can override all client properties. The other possible policies in the framework include `None` to disallow connectors from overriding client properties, and `Principal` to allow connectors to override only client principals.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>All</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="receive.buffer.bytes"></a><a id="connectconfigs_receive.buffer.bytes" href="#connectconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
+<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>32768 (32 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="request.timeout.ms"></a><a id="connectconfigs_request.timeout.ms" href="#connectconfigs_request.timeout.ms">request.timeout.ms</a></h4>
+<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>40000 (40 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.client.callback.handler.class"></a><a id="connectconfigs_sasl.client.callback.handler.class" href="#connectconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.jaas.config"></a><a id="connectconfigs_sasl.jaas.config" href="#connectconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
+<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.service.name"></a><a id="connectconfigs_sasl.kerberos.service.name" href="#connectconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
+<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.callback.handler.class"></a><a id="connectconfigs_sasl.login.callback.handler.class" href="#connectconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.class"></a><a id="connectconfigs_sasl.login.class" href="#connectconfigs_sasl.login.class">sasl.login.class</a></h4>
+<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.mechanism"></a><a id="connectconfigs_sasl.mechanism" href="#connectconfigs_sasl.mechanism">sasl.mechanism</a></h4>
+<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>GSSAPI</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="connectconfigs_sasl.oauthbearer.assertion.algorithm" href="#connectconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
+<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>RS256</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.aud" href="#connectconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
+<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.iss" href="#connectconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
+<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#connectconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
+<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.sub" href="#connectconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
+<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.file" href="#connectconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
+<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.private.key.file" href="#connectconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
+<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="connectconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#connectconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
+<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.template.file" href="#connectconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
+<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="connectconfigs_sasl.oauthbearer.client.credentials.client.id" href="#connectconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
+<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="connectconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#connectconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
+<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
+<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="connectconfigs_sasl.oauthbearer.jwt.retriever.class" href="#connectconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="connectconfigs_sasl.oauthbearer.jwt.validator.class" href="#connectconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.scope"></a><a id="connectconfigs_sasl.oauthbearer.scope" href="#connectconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
+<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="connectconfigs_sasl.oauthbearer.token.endpoint.url" href="#connectconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
+<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="security.protocol"></a><a id="connectconfigs_security.protocol" href="#connectconfigs_security.protocol">security.protocol</a></h4>
+<p>Protocol used to communicate with brokers.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>PLAINTEXT</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="send.buffer.bytes"></a><a id="connectconfigs_send.buffer.bytes" href="#connectconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
+<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.enabled.protocols"></a><a id="connectconfigs_ssl.enabled.protocols" href="#connectconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
+<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. Also see the config documentation for `ssl.protocol` to understand how it can impact the TLS version negotiation behavior.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.type"></a><a id="connectconfigs_ssl.keystore.type" href="#connectconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
+<p>The file format of the key store file. This is optional for client. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.protocol"></a><a id="connectconfigs_ssl.protocol" href="#connectconfigs_ssl.protocol">ssl.protocol</a></h4>
+<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in `ssl.enabled [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.provider"></a><a id="connectconfigs_ssl.provider" href="#connectconfigs_ssl.provider">ssl.provider</a></h4>
+<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.type"></a><a id="connectconfigs_ssl.truststore.type" href="#connectconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
+<p>The file format of the trust store file. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="worker.sync.timeout.ms"></a><a id="connectconfigs_worker.sync.timeout.ms" href="#connectconfigs_worker.sync.timeout.ms">worker.sync.timeout.ms</a></h4>
+<p>When the worker is out of sync with other workers and needs to resynchronize configurations, wait up to this amount of time before giving up, leaving the group, and waiting a backoff period before rejoining.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="worker.unsync.backoff.ms"></a><a id="connectconfigs_worker.unsync.backoff.ms" href="#connectconfigs_worker.unsync.backoff.ms">worker.unsync.backoff.ms</a></h4>
+<p>When the worker is out of sync with other workers and fails to catch up within worker.sync.timeout.ms, leave the Connect cluster for this long before rejoining.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="access.control.allow.methods"></a><a id="connectconfigs_access.control.allow.methods" href="#connectconfigs_access.control.allow.methods">access.control.allow.methods</a></h4>
+<p>Sets the methods supported for cross origin requests by setting the Access-Control-Allow-Methods header. The default value of the Access-Control-Allow-Methods header allows cross origin requests for GET, POST and HEAD.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="access.control.allow.origin"></a><a id="connectconfigs_access.control.allow.origin" href="#connectconfigs_access.control.allow.origin">access.control.allow.origin</a></h4>
+<p>Value to set the Access-Control-Allow-Origin header to for REST API requests.To enable cross origin access, set this to the domain of the application that should be permitted to access the API, or '*' to allow access from any domain. The default value only allows access from the domain of the REST API.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="admin.listeners"></a><a id="connectconfigs_admin.listeners" href="#connectconfigs_admin.listeners">admin.listeners</a></h4>
+<p>List of comma-separated URIs the Admin REST API will listen on. The supported protocols are HTTP and HTTPS. An empty or blank string will disable this feature. The default behavior is to use the regular listener (specified by the 'listeners' property).</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td>List of comma-separated URLs, ex: http://localhost:8080,https://localhost:8443.</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.id"></a><a id="connectconfigs_client.id" href="#connectconfigs_client.id">client.id</a></h4>
+<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="config.providers"></a><a id="connectconfigs_config.providers" href="#connectconfigs_config.providers">config.providers</a></h4>
+<p>Comma-separated names of <code>ConfigProvider</code> classes, loaded and used in the order specified. Implementing the interface <code>ConfigProvider</code> allows you to replace variable references in connector configurations, such as for externalized secrets. </p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="config.storage.replication.factor"></a><a id="connectconfigs_config.storage.replication.factor" href="#connectconfigs_config.storage.replication.factor">config.storage.replication.factor</a></h4>
+<p>Replication factor used when creating the configuration storage topic</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>3</td></tr>
+<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="connect.protocol"></a><a id="connectconfigs_connect.protocol" href="#connectconfigs_connect.protocol">connect.protocol</a></h4>
+<p>Compatibility mode for Kafka Connect Protocol</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>sessioned</td></tr>
+<tr><th>Valid Values:</th><td>[eager, compatible, sessioned]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="header.converter"></a><a id="connectconfigs_header.converter" href="#connectconfigs_header.converter">header.converter</a></h4>
+<p>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deserialize them by inferring the sche [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.connect.storage.SimpleHeaderConverter</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="header.converter.plugin.version"></a><a id="connectconfigs_header.converter.plugin.version" href="#connectconfigs_header.converter.plugin.version">header.converter.plugin.version</a></h4>
+<p>Version of the header converter.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="inter.worker.key.generation.algorithm"></a><a id="connectconfigs_inter.worker.key.generation.algorithm" href="#connectconfigs_inter.worker.key.generation.algorithm">inter.worker.key.generation.algorithm</a></h4>
+<p>The algorithm to use for generating internal request keys. The algorithm 'HmacSHA256' will be used as a default on JVMs that support it; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>HmacSHA256</td></tr>
+<tr><th>Valid Values:</th><td>Any KeyGenerator algorithm supported by the worker JVM</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="inter.worker.key.size"></a><a id="connectconfigs_inter.worker.key.size" href="#connectconfigs_inter.worker.key.size">inter.worker.key.size</a></h4>
+<p>The size of the key to use for signing internal requests, in bits. If null, the default key size for the key generation algorithm will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="inter.worker.key.ttl.ms"></a><a id="connectconfigs_inter.worker.key.ttl.ms" href="#connectconfigs_inter.worker.key.ttl.ms">inter.worker.key.ttl.ms</a></h4>
+<p>The TTL of generated session keys used for internal request validation (in milliseconds)</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="inter.worker.signature.algorithm"></a><a id="connectconfigs_inter.worker.signature.algorithm" href="#connectconfigs_inter.worker.signature.algorithm">inter.worker.signature.algorithm</a></h4>
+<p>The algorithm used to sign internal requestsThe algorithm 'inter.worker.signature.algorithm' will be used as a default on JVMs that support it; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>HmacSHA256</td></tr>
+<tr><th>Valid Values:</th><td>Any MAC algorithm supported by the worker JVM</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="inter.worker.verification.algorithms"></a><a id="connectconfigs_inter.worker.verification.algorithms" href="#connectconfigs_inter.worker.verification.algorithms">inter.worker.verification.algorithms</a></h4>
+<p>A list of permitted algorithms for verifying internal requests, which must include the algorithm used for the inter.worker.signature.algorithm property. The algorithm(s) '[HmacSHA256]' will be used as a default on JVMs that provide them; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>HmacSHA256</td></tr>
+<tr><th>Valid Values:</th><td>A list of one or more MAC algorithms, each supported by the worker JVM</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="key.converter.plugin.version"></a><a id="connectconfigs_key.converter.plugin.version" href="#connectconfigs_key.converter.plugin.version">key.converter.plugin.version</a></h4>
+<p>Version of the key converter.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="listeners"></a><a id="connectconfigs_listeners" href="#connectconfigs_listeners">listeners</a></h4>
+<p>List of comma-separated URIs the REST API will listen on. The supported protocols are HTTP and HTTPS.<br> Specify hostname as 0.0.0.0 to bind to all interfaces.<br> Leave hostname empty to bind to default interface.<br> Examples of legal listener lists: HTTP://myhost:8083,HTTPS://myhost:8084</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>http://:8083</td></tr>
+<tr><th>Valid Values:</th><td>List of comma-separated URLs, ex: http://localhost:8080,https://localhost:8443.</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.max.age.ms"></a><a id="connectconfigs_metadata.max.age.ms" href="#connectconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
+<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="connectconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#connectconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
+<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.strategy"></a><a id="connectconfigs_metadata.recovery.strategy" href="#connectconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
+<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>rebootstrap</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metric.reporters"></a><a id="connectconfigs_metric.reporters" href="#connectconfigs_metric.reporters">metric.reporters</a></h4>
+<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.num.samples"></a><a id="connectconfigs_metrics.num.samples" href="#connectconfigs_metrics.num.samples">metrics.num.samples</a></h4>
+<p>The number of samples maintained to compute metrics.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>2</td></tr>
+<tr><th>Valid Values:</th><td>[1,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.recording.level"></a><a id="connectconfigs_metrics.recording.level" href="#connectconfigs_metrics.recording.level">metrics.recording.level</a></h4>
+<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>INFO</td></tr>
+<tr><th>Valid Values:</th><td>[INFO, DEBUG]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.sample.window.ms"></a><a id="connectconfigs_metrics.sample.window.ms" href="#connectconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
+<p>The window of time a metrics sample is computed over.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="offset.flush.interval.ms"></a><a id="connectconfigs_offset.flush.interval.ms" href="#connectconfigs_offset.flush.interval.ms">offset.flush.interval.ms</a></h4>
+<p>Interval at which to try committing offsets for tasks.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="offset.flush.timeout.ms"></a><a id="connectconfigs_offset.flush.timeout.ms" href="#connectconfigs_offset.flush.timeout.ms">offset.flush.timeout.ms</a></h4>
+<p>Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. This property has no effect for source connectors running with exactly-once support.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="offset.storage.partitions"></a><a id="connectconfigs_offset.storage.partitions" href="#connectconfigs_offset.storage.partitions">offset.storage.partitions</a></h4>
+<p>The number of partitions used when creating the offset storage topic</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>25</td></tr>
+<tr><th>Valid Values:</th><td>Positive number, or -1 to use the broker's default</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="offset.storage.replication.factor"></a><a id="connectconfigs_offset.storage.replication.factor" href="#connectconfigs_offset.storage.replication.factor">offset.storage.replication.factor</a></h4>
+<p>Replication factor used when creating the offset storage topic</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>3</td></tr>
+<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="plugin.discovery"></a><a id="connectconfigs_plugin.discovery" href="#connectconfigs_plugin.discovery">plugin.discovery</a></h4>
+<p>Method to use to discover plugins present in the classpath and plugin.path configuration. This can be one of multiple values with the following meanings:<br>* only_scan: Discover plugins only by reflection. Plugins which are not discoverable by ServiceLoader will not impact worker startup.<br>* hybrid_warn: Discover plugins reflectively and by ServiceLoader. Plugins which are not discoverable by ServiceLoader will print warnings during worker startup.<br>* hybrid_fail: Discover plugin [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>hybrid_warn</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [ONLY_SCAN, SERVICE_LOAD, HYBRID_WARN, HYBRID_FAIL]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="plugin.path"></a><a id="connectconfigs_plugin.path" href="#connectconfigs_plugin.path">plugin.path</a></h4>
+<p>List of paths separated by commas (,) that contain plugins (connectors, converters, transformations). The list should consist of top level directories that include any combination of: <br>a) directories immediately containing jars with plugins and their dependencies<br>b) uber-jars with plugins and their dependencies<br>c) directories immediately containing the package directory structure of classes of plugins and their dependencies<br>Note: symlinks will be followed to discover depen [...]
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.max.ms"></a><a id="connectconfigs_reconnect.backoff.max.ms" href="#connectconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.ms"></a><a id="connectconfigs_reconnect.backoff.ms" href="#connectconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
+<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>50</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="response.http.headers.config"></a><a id="connectconfigs_response.http.headers.config" href="#connectconfigs_response.http.headers.config">response.http.headers.config</a></h4>
+<p>Rules for REST API HTTP response headers</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td>Comma-separated header rules, where each header rule is of the form '[action] [header name]:[header value]' and optionally surrounded by double quotes if any part of a header rule contains a comma</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="rest.advertised.host.name"></a><a id="connectconfigs_rest.advertised.host.name" href="#connectconfigs_rest.advertised.host.name">rest.advertised.host.name</a></h4>
+<p>If this is set, this is the hostname that will be given out to other workers to connect to.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="rest.advertised.listener"></a><a id="connectconfigs_rest.advertised.listener" href="#connectconfigs_rest.advertised.listener">rest.advertised.listener</a></h4>
+<p>Sets the advertised listener (HTTP or HTTPS) which will be given to other workers to use.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="rest.advertised.port"></a><a id="connectconfigs_rest.advertised.port" href="#connectconfigs_rest.advertised.port">rest.advertised.port</a></h4>
+<p>If this is set, this is the port that will be given out to other workers to connect to.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="rest.extension.classes"></a><a id="connectconfigs_rest.extension.classes" href="#connectconfigs_rest.extension.classes">rest.extension.classes</a></h4>
+<p>Comma-separated names of <code>ConnectRestExtension</code> classes, loaded and called in the order specified. Implementing the interface <code>ConnectRestExtension</code> allows you to inject into Connect's REST API user defined resources like filters. Typically used to add custom capability like logging, security, etc. </p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.max.ms"></a><a id="connectconfigs_retry.backoff.max.ms" href="#connectconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.ms"></a><a id="connectconfigs_retry.backoff.ms" href="#connectconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
+<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="connectconfigs_sasl.kerberos.kinit.cmd" href="#connectconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
+<p>Kerberos kinit command path.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="connectconfigs_sasl.kerberos.min.time.before.relogin" href="#connectconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
+<p>Login thread sleep time between refresh attempts.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>60000</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="connectconfigs_sasl.kerberos.ticket.renew.jitter" href="#connectconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
+<p>Percentage of random jitter added to the renewal time.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.05</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="connectconfigs_sasl.kerberos.ticket.renew.window.factor" href="#connectconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
+<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.connect.timeout.ms"></a><a id="connectconfigs_sasl.login.connect.timeout.ms" href="#connectconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.read.timeout.ms"></a><a id="connectconfigs_sasl.login.read.timeout.ms" href="#connectconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="connectconfigs_sasl.login.refresh.buffer.seconds" href="#connectconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
+<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>300</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="connectconfigs_sasl.login.refresh.min.period.seconds" href="#connectconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
+<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>60</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.window.factor"></a><a id="connectconfigs_sasl.login.refresh.window.factor" href="#connectconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
+<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.window.jitter"></a><a id="connectconfigs_sasl.login.refresh.window.jitter" href="#connectconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
+<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.05</td></tr>
+<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="connectconfigs_sasl.login.retry.backoff.max.ms" href="#connectconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
+<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.retry.backoff.ms"></a><a id="connectconfigs_sasl.login.retry.backoff.ms" href="#connectconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
+<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#connectconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
+<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>300</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#connectconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
+<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>60</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="connectconfigs_sasl.oauthbearer.clock.skew.seconds" href="#connectconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
+<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>30</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="connectconfigs_sasl.oauthbearer.expected.audience" href="#connectconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
+<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="connectconfigs_sasl.oauthbearer.expected.issuer" href="#connectconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
+<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="connectconfigs_sasl.oauthbearer.header.urlencode" href="#connectconfigs_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
+<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
+<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
+<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
+<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="connectconfigs_sasl.oauthbearer.scope.claim.name" href="#connectconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
+<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>scope</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="connectconfigs_sasl.oauthbearer.sub.claim.name" href="#connectconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
+<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>sub</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="scheduled.rebalance.max.delay.ms"></a><a id="connectconfigs_scheduled.rebalance.max.delay.ms" href="#connectconfigs_scheduled.rebalance.max.delay.ms">scheduled.rebalance.max.delay.ms</a></h4>
+<p>The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="connectconfigs_socket.connection.setup.timeout.max.ms" href="#connectconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
+<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.ms"></a><a id="connectconfigs_socket.connection.setup.timeout.ms" href="#connectconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
+<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.cipher.suites"></a><a id="connectconfigs_ssl.cipher.suites" href="#connectconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
+<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.client.auth"></a><a id="connectconfigs_ssl.client.auth" href="#connectconfigs_ssl.client.auth">ssl.client.auth</a></h4>
+<p>Configures kafka broker to request client authentication. The following settings are common: <ul> <li><code>ssl.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike required, if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authentication is not needed.</ul></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>none</td></tr>
+<tr><th>Valid Values:</th><td>[required, requested, none]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="connectconfigs_ssl.endpoint.identification.algorithm" href="#connectconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
+<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>https</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.engine.factory.class"></a><a id="connectconfigs_ssl.engine.factory.class" href="#connectconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
+<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keymanager.algorithm"></a><a id="connectconfigs_ssl.keymanager.algorithm" href="#connectconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
+<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>SunX509</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.secure.random.implementation"></a><a id="connectconfigs_ssl.secure.random.implementation" href="#connectconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
+<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.trustmanager.algorithm"></a><a id="connectconfigs_ssl.trustmanager.algorithm" href="#connectconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
+<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>PKIX</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="status.storage.partitions"></a><a id="connectconfigs_status.storage.partitions" href="#connectconfigs_status.storage.partitions">status.storage.partitions</a></h4>
+<p>The number of partitions used when creating the status storage topic</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>5</td></tr>
+<tr><th>Valid Values:</th><td>Positive number, or -1 to use the broker's default</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="status.storage.replication.factor"></a><a id="connectconfigs_status.storage.replication.factor" href="#connectconfigs_status.storage.replication.factor">status.storage.replication.factor</a></h4>
+<p>Replication factor used when creating the status storage topic</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>3</td></tr>
+<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="task.shutdown.graceful.timeout.ms"></a><a id="connectconfigs_task.shutdown.graceful.timeout.ms" href="#connectconfigs_task.shutdown.graceful.timeout.ms">task.shutdown.graceful.timeout.ms</a></h4>
+<p>Amount of time to wait for tasks to shutdown gracefully. This is the total amount of time, not per task. All task have shutdown triggered, then they are waited on sequentially.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="topic.creation.enable"></a><a id="connectconfigs_topic.creation.enable" href="#connectconfigs_topic.creation.enable">topic.creation.enable</a></h4>
+<p>Whether to allow automatic creation of topics used by source connectors, when source connectors are configured with `topic.creation.` properties. Each task will use an admin client to create its topics and will not depend on the Kafka brokers to create topics automatically.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="topic.tracking.allow.reset"></a><a id="connectconfigs_topic.tracking.allow.reset" href="#connectconfigs_topic.tracking.allow.reset">topic.tracking.allow.reset</a></h4>
+<p>If set to true, it allows user requests to reset the set of active topics per connector.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="topic.tracking.enable"></a><a id="connectconfigs_topic.tracking.enable" href="#connectconfigs_topic.tracking.enable">topic.tracking.enable</a></h4>
+<p>Enable tracking the set of active topics per connector during runtime.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="value.converter.plugin.version"></a><a id="connectconfigs_value.converter.plugin.version" href="#connectconfigs_value.converter.plugin.version">value.converter.plugin.version</a></h4>
+<p>Version of the value converter.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+</ul>
+
diff --git a/41/generated/connect_metrics.html b/41/generated/connect_metrics.html
new file mode 100644
index 000000000..d0e0f045d
--- /dev/null
+++ b/41/generated/connect_metrics.html
@@ -0,0 +1,463 @@
+<table class="data-table">
+<tbody>
+<tr>
+<th>Metric/Attribute name</th>
+<th>Description</th>
+<th>Mbean name</th>
+</tr>
+<tr>
+<td>connector-count</td>
+<td>The number of connectors run in this worker.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-startup-attempts-total</td>
+<td>The total number of connector startups that this worker has attempted.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-startup-failure-percentage</td>
+<td>The average percentage of this worker's connectors starts that failed.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-startup-failure-total</td>
+<td>The total number of connector starts that failed.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-startup-success-percentage</td>
+<td>The average percentage of this worker's connectors starts that succeeded.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-startup-success-total</td>
+<td>The total number of connector starts that succeeded.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-count</td>
+<td>The number of tasks run in this worker.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-startup-attempts-total</td>
+<td>The total number of task startups that this worker has attempted.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-startup-failure-percentage</td>
+<td>The average percentage of this worker's tasks starts that failed.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-startup-failure-total</td>
+<td>The total number of task starts that failed.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-startup-success-percentage</td>
+<td>The average percentage of this worker's tasks starts that succeeded.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>task-startup-success-total</td>
+<td>The total number of task starts that succeeded.</td>
+<td>kafka.connect:type=connect-worker-metrics</td>
+</tr>
+<tr>
+<td>connector-destroyed-task-count</td>
+<td>The number of destroyed tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-failed-task-count</td>
+<td>The number of failed tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-paused-task-count</td>
+<td>The number of paused tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-restarting-task-count</td>
+<td>The number of restarting tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-running-task-count</td>
+<td>The number of running tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-total-task-count</td>
+<td>The number of tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-unassigned-task-count</td>
+<td>The number of unassigned tasks of the connector on the worker.</td>
+<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>completed-rebalances-total</td>
+<td>The total number of rebalances completed by this worker.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>connect-protocol</td>
+<td>The Connect protocol used by this cluster</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>epoch</td>
+<td>The epoch or generation number of this worker.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>leader-name</td>
+<td>The name of the group leader.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>rebalance-avg-time-ms</td>
+<td>The average time in milliseconds spent by this worker to rebalance.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>rebalance-max-time-ms</td>
+<td>The maximum time in milliseconds spent by this worker to rebalance.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>rebalancing</td>
+<td>Whether this worker is currently rebalancing.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>time-since-last-rebalance-ms</td>
+<td>The time in milliseconds since this worker completed the most recent rebalance.</td>
+<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
+</tr>
+<tr>
+<td>connector-class</td>
+<td>The name of the connector class.</td>
+<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-type</td>
+<td>The type of the connector. One of 'source' or 'sink'.</td>
+<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>connector-version</td>
+<td>The version of the connector class, as reported by the connector.</td>
+<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>status</td>
+<td>The status of the connector. One of 'unassigned', 'running', 'paused', 'stopped', 'failed', or 'restarting'.</td>
+<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
+</tr>
+<tr>
+<td>predicate-class</td>
+<td>The class name of the predicate class</td>
+<td>kafka.connect:type=connector-predicate-metrics,connector="{connector}",task="{task}",predicate="{predicate}"</td>
+</tr>
+<tr>
+<td>predicate-version</td>
+<td>The version of the predicate class</td>
+<td>kafka.connect:type=connector-predicate-metrics,connector="{connector}",task="{task}",predicate="{predicate}"</td>
+</tr>
+<tr>
+<td>batch-size-avg</td>
+<td>The average number of records in the batches the task has processed so far.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>batch-size-max</td>
+<td>The number of records in the largest batch the task has processed so far.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>connector-class</td>
+<td>The name of the connector class.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>connector-type</td>
+<td>The type of the connector. One of 'source' or 'sink'.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>connector-version</td>
+<td>The version of the connector class, as reported by the connector.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>header-converter-class</td>
+<td>The fully qualified class name from header.converter</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>header-converter-version</td>
+<td>The version instantiated for header.converter. May be undefined</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>key-converter-class</td>
+<td>The fully qualified class name from key.converter</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>key-converter-version</td>
+<td>The version instantiated for key.converter. May be undefined</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-avg-time-ms</td>
+<td>The average time in milliseconds taken by this task to commit offsets.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-failure-percentage</td>
+<td>The average percentage of this task's offset commit attempts that failed.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-max-time-ms</td>
+<td>The maximum time in milliseconds taken by this task to commit offsets.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-success-percentage</td>
+<td>The average percentage of this task's offset commit attempts that succeeded.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>pause-ratio</td>
+<td>The fraction of time this task has spent in the pause state.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>running-ratio</td>
+<td>The fraction of time this task has spent in the running state.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>status</td>
+<td>The status of the connector task. One of 'unassigned', 'running', 'paused', 'failed', or 'restarting'.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>task-class</td>
+<td>The class name of the task.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>task-version</td>
+<td>The version of the task.</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>value-converter-class</td>
+<td>The fully qualified class name from value.converter</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>value-converter-version</td>
+<td>The version instantiated for value.converter. May be undefined</td>
+<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>transform-class</td>
+<td>The class name of the transformation class</td>
+<td>kafka.connect:type=connector-transform-metrics,connector="{connector}",task="{task}",transform="{transform}"</td>
+</tr>
+<tr>
+<td>transform-version</td>
+<td>The version of the transformation class</td>
+<td>kafka.connect:type=connector-transform-metrics,connector="{connector}",task="{task}",transform="{transform}"</td>
+</tr>
+<tr>
+<td>offset-commit-completion-rate</td>
+<td>The average per-second number of offset commit completions that were completed successfully.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-completion-total</td>
+<td>The total number of offset commit completions that were completed successfully.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-seq-no</td>
+<td>The current sequence number for offset commits.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-skip-rate</td>
+<td>The average per-second number of offset commit completions that were received too late and skipped/ignored.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>offset-commit-skip-total</td>
+<td>The total number of offset commit completions that were received too late and skipped/ignored.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>partition-count</td>
+<td>The number of topic partitions assigned to this task belonging to the named sink connector in this worker.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>put-batch-avg-time-ms</td>
+<td>The average time taken by this task to put a batch of sinks records.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>put-batch-max-time-ms</td>
+<td>The maximum time taken by this task to put a batch of sinks records.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-active-count</td>
+<td>The number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-active-count-avg</td>
+<td>The average number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-active-count-max</td>
+<td>The maximum number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-lag-max</td>
+<td>The maximum lag in terms of number of records that the sink task is behind the consumer's position for any topic partitions.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-read-rate</td>
+<td>The average per-second number of records read from Kafka for this task belonging to the named sink connector in this worker. This is before transformations are applied.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-read-total</td>
+<td>The total number of records read from Kafka by this task belonging to the named sink connector in this worker, since the task was last restarted.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-send-rate</td>
+<td>The average per-second number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker. This is after transformations are applied and excludes any records filtered out by the transformations.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>sink-record-send-total</td>
+<td>The total number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker, since the task was last restarted.</td>
+<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>poll-batch-avg-time-ms</td>
+<td>The average time in milliseconds taken by this task to poll for a batch of source records.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>poll-batch-max-time-ms</td>
+<td>The maximum time in milliseconds taken by this task to poll for a batch of source records.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-active-count</td>
+<td>The number of records that have been produced by this task but not yet completely written to Kafka.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-active-count-avg</td>
+<td>The average number of records that have been produced by this task but not yet completely written to Kafka.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-active-count-max</td>
+<td>The maximum number of records that have been produced by this task but not yet completely written to Kafka.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-poll-rate</td>
+<td>The average per-second number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-poll-total</td>
+<td>The total number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-write-rate</td>
+<td>The average per-second number of records written to Kafka for this task belonging to the named source connector in this worker, since the task was last restarted. This is after transformations are applied, and excludes any records filtered out by the transformations.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>source-record-write-total</td>
+<td>The number of records output written to Kafka for this task belonging to the named source connector in this worker, since the task was last restarted. This is after transformations are applied, and excludes any records filtered out by the transformations.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>transaction-size-avg</td>
+<td>The average number of records in the transactions the task has committed so far.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>transaction-size-max</td>
+<td>The number of records in the largest transaction the task has committed so far.</td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>transaction-size-min</td>
+<td>The number of records in the smallest transaction the task has committed so far. </td>
+<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>deadletterqueue-produce-failures</td>
+<td>The number of failed writes to the dead letter queue.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>deadletterqueue-produce-requests</td>
+<td>The number of attempted writes to the dead letter queue.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>last-error-timestamp</td>
+<td>The epoch timestamp when this task last encountered an error.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>total-errors-logged</td>
+<td>The number of errors that were logged.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>total-record-errors</td>
+<td>The number of record processing errors in this task. </td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>total-record-failures</td>
+<td>The number of record processing failures in this task.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>total-records-skipped</td>
+<td>The number of records skipped due to errors.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+<tr>
+<td>total-retries</td>
+<td>The number of operations retried.</td>
+<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
+</tr>
+</tbody></table>
diff --git a/41/generated/connect_predicates.html b/41/generated/connect_predicates.html
new file mode 100644
index 000000000..7a26dc6bb
--- /dev/null
+++ b/41/generated/connect_predicates.html
@@ -0,0 +1,45 @@
+<div id="org.apache.kafka.connect.transforms.predicates.HasHeaderKey">
+<h5><a href="#org.apache.kafka.connect.transforms.predicates.HasHeaderKey">org.apache.kafka.connect.transforms.predicates.HasHeaderKey</a></h5>
+A predicate which is true for records with at least one header with the configured name.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="name"></a><a id="org.apache.kafka.connect.transforms.predicates.HasHeaderKey_name" href="#org.apache.kafka.connect.transforms.predicates.HasHeaderKey_name">name</a></h6>
+<p>The header name.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty string</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.predicates.RecordIsTombstone">
+<h5><a href="#org.apache.kafka.connect.transforms.predicates.RecordIsTombstone">org.apache.kafka.connect.transforms.predicates.RecordIsTombstone</a></h5>
+A predicate which is true for records which are tombstones (i.e. have null value).
+<p/>
+<ul class="config-list">
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.predicates.TopicNameMatches">
+<h5><a href="#org.apache.kafka.connect.transforms.predicates.TopicNameMatches">org.apache.kafka.connect.transforms.predicates.TopicNameMatches</a></h5>
+A predicate which is true for records with a topic name that matches the configured regular expression.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="pattern"></a><a id="org.apache.kafka.connect.transforms.predicates.TopicNameMatches_pattern" href="#org.apache.kafka.connect.transforms.predicates.TopicNameMatches_pattern">pattern</a></h6>
+<p>A Java regular expression for matching against the name of a record's topic.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty string, valid regex</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+
diff --git a/41/generated/connect_rest.yaml b/41/generated/connect_rest.yaml
new file mode 100644
index 000000000..79f59295c
--- /dev/null
+++ b/41/generated/connect_rest.yaml
@@ -0,0 +1,715 @@
+openapi: 3.0.0
+info:
+ contact:
+ email: dev@kafka.apache.org
+ description: "This is the documentation of the [Apache Kafka](https://kafka.apache.org)\
+ \ Connect REST API."
+ license:
+ name: Apache 2.0
+ url: https://www.apache.org/licenses/LICENSE-2.0.html
+ title: Kafka Connect REST API
+ version: 4.1.0
+paths:
+ /:
+ get:
+ operationId: serverInfo
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ServerInfo"
+ description: default response
+ summary: Get details about this Connect worker and the ID of the Kafka cluster
+ it is connected to
+ /admin/loggers:
+ get:
+ operationId: listLoggers
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: List the current loggers that have their levels explicitly set and
+ their log levels
+ /admin/loggers/{logger}:
+ get:
+ operationId: getLogger
+ parameters:
+ - in: path
+ name: logger
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Get the log level for the specified logger
+ put:
+ operationId: setLevel
+ parameters:
+ - in: path
+ name: logger
+ required: true
+ schema:
+ type: string
+ - description: "The scope for the logging modification (single-worker, cluster-wide,\
+ \ etc.)"
+ in: query
+ name: scope
+ schema:
+ type: string
+ default: worker
+ requestBody:
+ content:
+ application/json:
+ schema:
+ type: object
+ additionalProperties:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Set the log level for the specified logger
+ /connector-plugins:
+ get:
+ operationId: listConnectorPlugins
+ parameters:
+ - description: Whether to list only connectors instead of all plugins
+ in: query
+ name: connectorsOnly
+ schema:
+ type: boolean
+ default: true
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ type: array
+ items:
+ $ref: "#/components/schemas/PluginInfo"
+ description: default response
+ summary: List all connector plugins installed
+ /connector-plugins/{pluginName}/config:
+ get:
+ operationId: getConnectorConfigDef
+ parameters:
+ - in: path
+ name: pluginName
+ required: true
+ schema:
+ type: string
+ - in: query
+ name: version
+ schema:
+ type: string
+ default: latest
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ type: array
+ items:
+ $ref: "#/components/schemas/ConfigKeyInfo"
+ description: default response
+ summary: Get the configuration definition for the specified pluginName
+ /connector-plugins/{pluginName}/config/validate:
+ put:
+ operationId: validateConfigs
+ parameters:
+ - in: path
+ name: pluginName
+ required: true
+ schema:
+ type: string
+ requestBody:
+ content:
+ application/json:
+ schema:
+ type: object
+ additionalProperties:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ConfigInfos"
+ description: default response
+ summary: Validate the provided configuration against the configuration definition
+ for the specified pluginName
+ /connectors:
+ get:
+ operationId: listConnectors
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: List all active connectors
+ post:
+ operationId: createConnector
+ requestBody:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/CreateConnectorRequest"
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Create a new connector
+ /connectors/{connector}:
+ delete:
+ operationId: destroyConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Delete the specified connector
+ get:
+ operationId: getConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ConnectorInfo"
+ description: default response
+ summary: Get the details for the specified connector
+ /connectors/{connector}/config:
+ get:
+ operationId: getConnectorConfig
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ type: object
+ additionalProperties:
+ type: string
+ description: default response
+ summary: Get the configuration for the specified connector
+ patch:
+ operationId: patchConnectorConfig
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ requestBody:
+ content:
+ application/json:
+ schema:
+ type: object
+ additionalProperties:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ put:
+ operationId: putConnectorConfig
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ requestBody:
+ content:
+ application/json:
+ schema:
+ type: object
+ additionalProperties:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Create or reconfigure the specified connector
+ /connectors/{connector}/offsets:
+ delete:
+ operationId: resetConnectorOffsets
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Reset the offsets for the specified connector
+ get:
+ operationId: getOffsets
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ConnectorOffsets"
+ description: default response
+ summary: Get the current offsets for the specified connector
+ patch:
+ operationId: alterConnectorOffsets
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ requestBody:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ConnectorOffsets"
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Alter the offsets for the specified connector
+ /connectors/{connector}/pause:
+ put:
+ description: This operation is idempotent and has no effects if the connector
+ is already paused
+ operationId: pauseConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Pause the specified connector
+ /connectors/{connector}/restart:
+ post:
+ operationId: restartConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ - description: Whether to also restart tasks
+ in: query
+ name: includeTasks
+ schema:
+ type: boolean
+ default: false
+ - description: Whether to only restart failed tasks/connectors
+ in: query
+ name: onlyFailed
+ schema:
+ type: boolean
+ default: false
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Restart the specified connector
+ /connectors/{connector}/resume:
+ put:
+ description: This operation is idempotent and has no effects if the connector
+ is already running
+ operationId: resumeConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Resume the specified connector
+ /connectors/{connector}/status:
+ get:
+ operationId: getConnectorStatus
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ConnectorStateInfo"
+ description: default response
+ summary: Get the status for the specified connector
+ /connectors/{connector}/stop:
+ put:
+ description: This operation is idempotent and has no effects if the connector
+ is already stopped
+ operationId: stopConnector
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Stop the specified connector
+ /connectors/{connector}/tasks:
+ get:
+ operationId: getTaskConfigs
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ type: array
+ items:
+ $ref: "#/components/schemas/TaskInfo"
+ description: default response
+ summary: List all tasks and their configurations for the specified connector
+ /connectors/{connector}/tasks/{task}/restart:
+ post:
+ operationId: restartTask
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ - in: path
+ name: task
+ required: true
+ schema:
+ type: integer
+ format: int32
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Restart the specified task for the specified connector
+ /connectors/{connector}/tasks/{task}/status:
+ get:
+ operationId: getTaskStatus
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ - in: path
+ name: task
+ required: true
+ schema:
+ type: integer
+ format: int32
+ responses:
+ default:
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/TaskState"
+ description: default response
+ summary: Get the state of the specified task for the specified connector
+ /connectors/{connector}/topics:
+ get:
+ operationId: getConnectorActiveTopics
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Get the list of topics actively used by the specified connector
+ /connectors/{connector}/topics/reset:
+ put:
+ operationId: resetConnectorActiveTopics
+ parameters:
+ - in: path
+ name: connector
+ required: true
+ schema:
+ type: string
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Reset the list of topics actively used by the specified connector
+ /health:
+ get:
+ operationId: healthCheck
+ responses:
+ default:
+ content:
+ application/json: {}
+ description: default response
+ summary: Health check endpoint to verify worker readiness and liveness
+components:
+ schemas:
+ ConfigInfo:
+ type: object
+ properties:
+ definition:
+ $ref: "#/components/schemas/ConfigKeyInfo"
+ value:
+ $ref: "#/components/schemas/ConfigValueInfo"
+ ConfigInfos:
+ type: object
+ properties:
+ configs:
+ type: array
+ items:
+ $ref: "#/components/schemas/ConfigInfo"
+ error_count:
+ type: integer
+ format: int32
+ groups:
+ type: array
+ items:
+ type: string
+ name:
+ type: string
+ ConfigKeyInfo:
+ type: object
+ properties:
+ default_value:
+ type: string
+ dependents:
+ type: array
+ items:
+ type: string
+ display_name:
+ type: string
+ documentation:
+ type: string
+ group:
+ type: string
+ importance:
+ type: string
+ name:
+ type: string
+ order:
+ type: integer
+ format: int32
+ order_in_group:
+ type: integer
+ format: int32
+ writeOnly: true
+ required:
+ type: boolean
+ type:
+ type: string
+ width:
+ type: string
+ ConfigValueInfo:
+ type: object
+ properties:
+ errors:
+ type: array
+ items:
+ type: string
+ name:
+ type: string
+ recommended_values:
+ type: array
+ items:
+ type: string
+ value:
+ type: string
+ visible:
+ type: boolean
+ ConnectorInfo:
+ type: object
+ properties:
+ config:
+ type: object
+ additionalProperties:
+ type: string
+ name:
+ type: string
+ tasks:
+ type: array
+ items:
+ $ref: "#/components/schemas/ConnectorTaskId"
+ type:
+ type: string
+ enum:
+ - source
+ - sink
+ - unknown
+ ConnectorOffset:
+ type: object
+ properties:
+ offset:
+ type: object
+ additionalProperties:
+ type: object
+ partition:
+ type: object
+ additionalProperties:
+ type: object
+ ConnectorOffsets:
+ type: object
+ properties:
+ offsets:
+ type: array
+ items:
+ $ref: "#/components/schemas/ConnectorOffset"
+ ConnectorState:
+ type: object
+ properties:
+ msg:
+ type: string
+ writeOnly: true
+ state:
+ type: string
+ trace:
+ type: string
+ version:
+ type: string
+ worker_id:
+ type: string
+ ConnectorStateInfo:
+ type: object
+ properties:
+ connector:
+ $ref: "#/components/schemas/ConnectorState"
+ name:
+ type: string
+ tasks:
+ type: array
+ items:
+ $ref: "#/components/schemas/TaskState"
+ type:
+ type: string
+ enum:
+ - source
+ - sink
+ - unknown
+ ConnectorTaskId:
+ type: object
+ properties:
+ connector:
+ type: string
+ task:
+ type: integer
+ format: int32
+ CreateConnectorRequest:
+ type: object
+ properties:
+ config:
+ type: object
+ additionalProperties:
+ type: string
+ initial_state:
+ type: string
+ enum:
+ - RUNNING
+ - PAUSED
+ - STOPPED
+ name:
+ type: string
+ PluginInfo:
+ type: object
+ properties:
+ class:
+ type: string
+ type:
+ type: string
+ version:
+ type: string
+ ServerInfo:
+ type: object
+ properties:
+ commit:
+ type: string
+ kafka_cluster_id:
+ type: string
+ version:
+ type: string
+ TaskInfo:
+ type: object
+ properties:
+ config:
+ type: object
+ additionalProperties:
+ type: string
+ id:
+ $ref: "#/components/schemas/ConnectorTaskId"
+ TaskState:
+ type: object
+ properties:
+ id:
+ type: integer
+ format: int32
+ msg:
+ type: string
+ writeOnly: true
+ state:
+ type: string
+ trace:
+ type: string
+ version:
+ type: string
+ worker_id:
+ type: string
diff --git a/41/generated/connect_transforms.html b/41/generated/connect_transforms.html
new file mode 100644
index 000000000..27f20bbcc
--- /dev/null
+++ b/41/generated/connect_transforms.html
@@ -0,0 +1,549 @@
+<div id="org.apache.kafka.connect.transforms.Cast">
+<h5><a href="#org.apache.kafka.connect.transforms.Cast">org.apache.kafka.connect.transforms.Cast</a></h5>
+Cast fields or the entire key or value to a specific type, e.g. to force an integer field to a smaller width. Cast from integers, floats, boolean and string to any other type, and cast binary to string (base64 encoded).<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Cast$Key</code>) or value (<code>org.apache.kafka.connect.transforms.Cast$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="spec"></a><a id="org.apache.kafka.connect.transforms.Cast_spec" href="#org.apache.kafka.connect.transforms.Cast_spec">spec</a></h6>
+<p>List of fields and the type to cast them to of the form field1:type,field2:type to cast fields of Maps or Structs. A single type to cast the entire value. Valid types are int8, int16, int32, int64, float32, float64, boolean, and string. Note that binary fields can only be cast to string.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.Cast_replace.null.with.default" href="#org.apache.kafka.connect.transforms.Cast_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.DropHeaders">
+<h5><a href="#org.apache.kafka.connect.transforms.DropHeaders">org.apache.kafka.connect.transforms.DropHeaders</a></h5>
+Removes one or more headers from each record.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="headers"></a><a id="org.apache.kafka.connect.transforms.DropHeaders_headers" href="#org.apache.kafka.connect.transforms.DropHeaders_headers">headers</a></h6>
+<p>The name of the headers to be removed.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty list</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.ExtractField">
+<h5><a href="#org.apache.kafka.connect.transforms.ExtractField">org.apache.kafka.connect.transforms.ExtractField</a></h5>
+Extract the specified field from a Struct when schema present, or a Map in the case of schemaless data. Any null values are passed through unmodified.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ExtractField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ExtractField$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.ExtractField_field" href="#org.apache.kafka.connect.transforms.ExtractField_field">field</a></h6>
+<p>Field name to extract.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="field.syntax.version"></a><a id="org.apache.kafka.connect.transforms.ExtractField_field.syntax.version" href="#org.apache.kafka.connect.transforms.ExtractField_field.syntax.version">field.syntax.version</a></h6>
+<p>Defines the version of the syntax to access fields. If set to `V1`, then the field paths are limited to access the elements at the root level of the struct or map. If set to `V2`, the syntax will support accessing nested elements. To access nested elements, dotted notation is used. If dots are already included in the field name, then backtick pairs can be used to wrap field names containing dots. E.g. to access the subfield `baz` from a field named "foo.bar" in a struct/map the follow [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>V1</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [V1, V2]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ExtractField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ExtractField_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.Filter">
+<h5><a href="#org.apache.kafka.connect.transforms.Filter">org.apache.kafka.connect.transforms.Filter</a></h5>
+Drops all records, filtering them from subsequent transformations in the chain. This is intended to be used conditionally to filter out records matching (or not matching) a particular Predicate.
+<p/>
+<ul class="config-list">
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.Flatten">
+<h5><a href="#org.apache.kafka.connect.transforms.Flatten">org.apache.kafka.connect.transforms.Flatten</a></h5>
+Flatten a nested data structure, generating names for each field by concatenating the field names at each level with a configurable delimiter character. Applies to Struct when schema present, or a Map in the case of schemaless data. Array fields and their contents are not modified. The default delimiter is '.'.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Flatten$Key</code>) or value (<code>org.apache.kafka.connect.transfo [...]
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="delimiter"></a><a id="org.apache.kafka.connect.transforms.Flatten_delimiter" href="#org.apache.kafka.connect.transforms.Flatten_delimiter">delimiter</a></h6>
+<p>Delimiter to insert between field names from the input record when generating field names for the output record</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>.</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.HeaderFrom">
+<h5><a href="#org.apache.kafka.connect.transforms.HeaderFrom">org.apache.kafka.connect.transforms.HeaderFrom</a></h5>
+Moves or copies fields in the key/value of a record into that record's headers. Corresponding elements of <code>fields</code> and <code>headers</code> together identify a field and the header it should be moved or copied to. Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.HeaderFrom$Key</code>) or value (<code>org.apache.kafka.connect.transforms.HeaderFrom$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_fields" href="#org.apache.kafka.connect.transforms.HeaderFrom_fields">fields</a></h6>
+<p>Field names in the record whose values are to be copied or moved to headers.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty list</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="headers"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_headers" href="#org.apache.kafka.connect.transforms.HeaderFrom_headers">headers</a></h6>
+<p>Header names, in the same order as the field names listed in the fields configuration property.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty list</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="operation"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_operation" href="#org.apache.kafka.connect.transforms.HeaderFrom_operation">operation</a></h6>
+<p>Either <code>move</code> if the fields are to be moved to the headers (removed from the key/value), or <code>copy</code> if the fields are to be copied to the headers (retained in the key/value).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>[move, copy]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_replace.null.with.default" href="#org.apache.kafka.connect.transforms.HeaderFrom_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.HoistField">
+<h5><a href="#org.apache.kafka.connect.transforms.HoistField">org.apache.kafka.connect.transforms.HoistField</a></h5>
+Wrap data using the specified field name in a Struct when schema present, or a Map in the case of schemaless data.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.HoistField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.HoistField$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.HoistField_field" href="#org.apache.kafka.connect.transforms.HoistField_field">field</a></h6>
+<p>Field name for the single field that will be created in the resulting Struct or Map.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.InsertField">
+<h5><a href="#org.apache.kafka.connect.transforms.InsertField">org.apache.kafka.connect.transforms.InsertField</a></h5>
+Insert field(s) using attributes from the record metadata or a configured static value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.InsertField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.InsertField$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="offset.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_offset.field" href="#org.apache.kafka.connect.transforms.InsertField_offset.field">offset.field</a></h6>
+<p>Field name for Kafka offset - only applicable to sink connectors.<br/>Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="partition.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_partition.field" href="#org.apache.kafka.connect.transforms.InsertField_partition.field">partition.field</a></h6>
+<p>Field name for Kafka partition. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.InsertField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.InsertField_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="static.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_static.field" href="#org.apache.kafka.connect.transforms.InsertField_static.field">static.field</a></h6>
+<p>Field name for static data field. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="static.value"></a><a id="org.apache.kafka.connect.transforms.InsertField_static.value" href="#org.apache.kafka.connect.transforms.InsertField_static.value">static.value</a></h6>
+<p>Static field value, if field name configured.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="timestamp.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_timestamp.field" href="#org.apache.kafka.connect.transforms.InsertField_timestamp.field">timestamp.field</a></h6>
+<p>Field name for record timestamp. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="topic.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_topic.field" href="#org.apache.kafka.connect.transforms.InsertField_topic.field">topic.field</a></h6>
+<p>Field name for Kafka topic. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.InsertHeader">
+<h5><a href="#org.apache.kafka.connect.transforms.InsertHeader">org.apache.kafka.connect.transforms.InsertHeader</a></h5>
+Add a header to each record.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="header"></a><a id="org.apache.kafka.connect.transforms.InsertHeader_header" href="#org.apache.kafka.connect.transforms.InsertHeader_header">header</a></h6>
+<p>The name of the header.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="value.literal"></a><a id="org.apache.kafka.connect.transforms.InsertHeader_value.literal" href="#org.apache.kafka.connect.transforms.InsertHeader_value.literal">value.literal</a></h6>
+<p>The literal value that is to be set as the header value on all records.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.MaskField">
+<h5><a href="#org.apache.kafka.connect.transforms.MaskField">org.apache.kafka.connect.transforms.MaskField</a></h5>
+Mask specified fields with a valid null value for the field type (i.e. 0, false, empty string, and so on).<p/>For numeric and string fields, an optional replacement value can be specified that is converted to the correct type.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.MaskField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.MaskField$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.MaskField_fields" href="#org.apache.kafka.connect.transforms.MaskField_fields">fields</a></h6>
+<p>Names of fields to mask.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty list</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.MaskField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.MaskField_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replacement"></a><a id="org.apache.kafka.connect.transforms.MaskField_replacement" href="#org.apache.kafka.connect.transforms.MaskField_replacement">replacement</a></h6>
+<p>Custom value replacement, that will be applied to all 'fields' values (numeric or non-empty string values only).</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td>non-empty string</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.RegexRouter">
+<h5><a href="#org.apache.kafka.connect.transforms.RegexRouter">org.apache.kafka.connect.transforms.RegexRouter</a></h5>
+Update the record topic using the configured regular expression and replacement string.<p/>Under the hood, the regex is compiled to a <code>java.util.regex.Pattern</code>. If the pattern matches the input topic, <code>java.util.regex.Matcher#replaceFirst()</code> is used with the replacement string to obtain the new topic.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="regex"></a><a id="org.apache.kafka.connect.transforms.RegexRouter_regex" href="#org.apache.kafka.connect.transforms.RegexRouter_regex">regex</a></h6>
+<p>Regular expression to use for matching.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>valid regex</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replacement"></a><a id="org.apache.kafka.connect.transforms.RegexRouter_replacement" href="#org.apache.kafka.connect.transforms.RegexRouter_replacement">replacement</a></h6>
+<p>Replacement string.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.ReplaceField">
+<h5><a href="#org.apache.kafka.connect.transforms.ReplaceField">org.apache.kafka.connect.transforms.ReplaceField</a></h5>
+Filter or rename fields.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ReplaceField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ReplaceField$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="exclude"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_exclude" href="#org.apache.kafka.connect.transforms.ReplaceField_exclude">exclude</a></h6>
+<p>Fields to exclude. This takes precedence over the fields to include.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="include"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_include" href="#org.apache.kafka.connect.transforms.ReplaceField_include">include</a></h6>
+<p>Fields to include. If specified, only these fields will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="renames"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_renames" href="#org.apache.kafka.connect.transforms.ReplaceField_renames">renames</a></h6>
+<p>Field rename mappings.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ReplaceField_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.SetSchemaMetadata">
+<h5><a href="#org.apache.kafka.connect.transforms.SetSchemaMetadata">org.apache.kafka.connect.transforms.SetSchemaMetadata</a></h5>
+Set the schema name, version or both on the record's key (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Key</code>) or value (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Value</code>) schema.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="schema.name"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.name" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.name">schema.name</a></h6>
+<p>Schema name to set.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="schema.version"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.version" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.version">schema.version</a></h6>
+<p>Schema version to set.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_replace.null.with.default" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.TimestampConverter">
+<h5><a href="#org.apache.kafka.connect.transforms.TimestampConverter">org.apache.kafka.connect.transforms.TimestampConverter</a></h5>
+Convert timestamps between different formats such as Unix epoch, strings, and Connect Date/Timestamp types.Applies to individual fields or to the entire value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.TimestampConverter$Key</code>) or value (<code>org.apache.kafka.connect.transforms.TimestampConverter$Value</code>).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="target.type"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_target.type" href="#org.apache.kafka.connect.transforms.TimestampConverter_target.type">target.type</a></h6>
+<p>The desired timestamp representation: string, unix, Date, Time, or Timestamp</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>[string, unix, Date, Time, Timestamp]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_field" href="#org.apache.kafka.connect.transforms.TimestampConverter_field">field</a></h6>
+<p>The field containing the timestamp, or empty if the entire value is a timestamp</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="format"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_format" href="#org.apache.kafka.connect.transforms.TimestampConverter_format">format</a></h6>
+<p>A SimpleDateFormat-compatible format for the timestamp. Used to generate the output when type=string or used to parse the input if the input is a string.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_replace.null.with.default" href="#org.apache.kafka.connect.transforms.TimestampConverter_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="unix.precision"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_unix.precision" href="#org.apache.kafka.connect.transforms.TimestampConverter_unix.precision">unix.precision</a></h6>
+<p>The desired Unix precision for the timestamp: seconds, milliseconds, microseconds, or nanoseconds. Used to generate the output when type=unix or used to parse the input if the input is a Long.Note: This SMT will cause precision loss during conversions from, and to, values with sub-millisecond components.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>milliseconds</td></tr>
+<tr><th>Valid Values:</th><td>[nanoseconds, microseconds, milliseconds, seconds]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.TimestampRouter">
+<h5><a href="#org.apache.kafka.connect.transforms.TimestampRouter">org.apache.kafka.connect.transforms.TimestampRouter</a></h5>
+Update the record's topic field as a function of the original topic value and the record timestamp.<p/>This is mainly useful for sink connectors, since the topic field is often used to determine the equivalent entity name in the destination system(e.g. database table or search index name).
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="timestamp.format"></a><a id="org.apache.kafka.connect.transforms.TimestampRouter_timestamp.format" href="#org.apache.kafka.connect.transforms.TimestampRouter_timestamp.format">timestamp.format</a></h6>
+<p>Format string for the timestamp that is compatible with <code>java.text.SimpleDateFormat</code>.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>yyyyMMdd</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="topic.format"></a><a id="org.apache.kafka.connect.transforms.TimestampRouter_topic.format" href="#org.apache.kafka.connect.transforms.TimestampRouter_topic.format">topic.format</a></h6>
+<p>Format string which can contain <code>${topic}</code> and <code>${timestamp}</code> as placeholders for the topic and timestamp, respectively.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>${topic}-${timestamp}</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+<div id="org.apache.kafka.connect.transforms.ValueToKey">
+<h5><a href="#org.apache.kafka.connect.transforms.ValueToKey">org.apache.kafka.connect.transforms.ValueToKey</a></h5>
+Replace the record key with a new key formed from a subset of fields in the record value.
+<p/>
+<ul class="config-list">
+<li>
+<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.ValueToKey_fields" href="#org.apache.kafka.connect.transforms.ValueToKey_fields">fields</a></h6>
+<p>Field names on the record value to extract as the record key.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td>non-empty list</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ValueToKey_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ValueToKey_replace.null.with.default">replace.null.with.default</a></h6>
+<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+</ul>
+
+</div>
+
diff --git a/41/generated/consumer_config.html b/41/generated/consumer_config.html
new file mode 100644
index 000000000..58333b038
--- /dev/null
+++ b/41/generated/consumer_config.html
@@ -0,0 +1,1133 @@
+<ul class="config-list">
+<li>
+<h4><a id="key.deserializer"></a><a id="consumerconfigs_key.deserializer" href="#consumerconfigs_key.deserializer">key.deserializer</a></h4>
+<p>Deserializer class for key that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="value.deserializer"></a><a id="consumerconfigs_value.deserializer" href="#consumerconfigs_value.deserializer">value.deserializer</a></h4>
+<p>Deserializer class for value that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td></td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="bootstrap.servers"></a><a id="consumerconfigs_bootstrap.servers" href="#consumerconfigs_bootstrap.servers">bootstrap.servers</a></h4>
+<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="fetch.min.bytes"></a><a id="consumerconfigs_fetch.min.bytes" href="#consumerconfigs_fetch.min.bytes">fetch.min.bytes</a></h4>
+<p>The minimum amount of data the server should return for a fetch request. If insufficient data is available the request will wait for that much data to accumulate before answering the request. The default setting of 1 byte means that fetch requests are answered as soon as that many byte(s) of data is available or the fetch request times out waiting for data to arrive. Setting this to a larger value will cause the server to wait for larger amounts of data to accumulate which can improve [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>1</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="group.id"></a><a id="consumerconfigs_group.id" href="#consumerconfigs_group.id">group.id</a></h4>
+<p>A unique string that identifies the consumer group this consumer belongs to. This property is required if the consumer uses either the group management functionality by using <code>subscribe(topic)</code> or the Kafka-based offset management strategy.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="group.protocol"></a><a id="consumerconfigs_group.protocol" href="#consumerconfigs_group.protocol">group.protocol</a></h4>
+<p>The group protocol consumer should use. We currently support "classic" or "consumer". If "consumer" is specified, then the consumer group protocol will be used. Otherwise, the classic group protocol will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>classic</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [CONSUMER, CLASSIC]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="heartbeat.interval.ms"></a><a id="consumerconfigs_heartbeat.interval.ms" href="#consumerconfigs_heartbeat.interval.ms">heartbeat.interval.ms</a></h4>
+<p>The expected time between heartbeats to the consumer coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the consumer's session stays active and to facilitate rebalancing when new consumers join or leave the group. This config is only supported if <code>group.protocol</code> is set to "classic". In that case, the value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="max.partition.fetch.bytes"></a><a id="consumerconfigs_max.partition.fetch.bytes" href="#consumerconfigs_max.partition.fetch.bytes">max.partition.fetch.bytes</a></h4>
+<p>The maximum amount of data per-partition the server will return. Records are fetched in batches by the consumer. If the first record batch in the first non-empty partition of the fetch is larger than this limit, the batch will still be returned to ensure that the consumer can make progress. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic config). See fetch.max.bytes for limiting [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="session.timeout.ms"></a><a id="consumerconfigs_session.timeout.ms" href="#consumerconfigs_session.timeout.ms">session.timeout.ms</a></h4>
+<p>The timeout used to detect client failures when using Kafka's group management facility. The client sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove this client from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min.session.timeout.ms</code> and <code>gro [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.key.password"></a><a id="consumerconfigs_ssl.key.password" href="#consumerconfigs_ssl.key.password">ssl.key.password</a></h4>
+<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.certificate.chain"></a><a id="consumerconfigs_ssl.keystore.certificate.chain" href="#consumerconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
+<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.key"></a><a id="consumerconfigs_ssl.keystore.key" href="#consumerconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
+<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.location"></a><a id="consumerconfigs_ssl.keystore.location" href="#consumerconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
+<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.password"></a><a id="consumerconfigs_ssl.keystore.password" href="#consumerconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
+<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.certificates"></a><a id="consumerconfigs_ssl.truststore.certificates" href="#consumerconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
+<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.location"></a><a id="consumerconfigs_ssl.truststore.location" href="#consumerconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
+<p>The location of the trust store file.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.password"></a><a id="consumerconfigs_ssl.truststore.password" href="#consumerconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
+<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>high</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="allow.auto.create.topics"></a><a id="consumerconfigs_allow.auto.create.topics" href="#consumerconfigs_allow.auto.create.topics">allow.auto.create.topics</a></h4>
+<p>Allow automatic topic creation on the broker when subscribing to or assigning a topic. A topic being subscribed to will be automatically created only if the broker allows for it using `auto.create.topics.enable` broker configuration.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="auto.offset.reset"></a><a id="consumerconfigs_auto.offset.reset" href="#consumerconfigs_auto.offset.reset">auto.offset.reset</a></h4>
+<p>What to do when there is no initial offset in Kafka or if the current offset does not exist any more on the server (e.g. because that data has been deleted): <ul><li>earliest: automatically reset the offset to the earliest offset</li><li>latest: automatically reset the offset to the latest offset</li><li>by_duration:<duration>: automatically reset the offset to a configured <duration> from the current timestamp. <duration> must be specified in ISO8601 format (PnDTnHn [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>latest</td></tr>
+<tr><th>Valid Values:</th><td>[latest, earliest, none, by_duration:PnDTnHnMn.nS]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.dns.lookup"></a><a id="consumerconfigs_client.dns.lookup" href="#consumerconfigs_client.dns.lookup">client.dns.lookup</a></h4>
+<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
+<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="connections.max.idle.ms"></a><a id="consumerconfigs_connections.max.idle.ms" href="#consumerconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
+<p>Close idle connections after the number of milliseconds specified by this config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>540000 (9 minutes)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="default.api.timeout.ms"></a><a id="consumerconfigs_default.api.timeout.ms" href="#consumerconfigs_default.api.timeout.ms">default.api.timeout.ms</a></h4>
+<p>Specifies the timeout (in milliseconds) for client APIs. This configuration is used as the default timeout for all client operations that do not specify a <code>timeout</code> parameter.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="enable.auto.commit"></a><a id="consumerconfigs_enable.auto.commit" href="#consumerconfigs_enable.auto.commit">enable.auto.commit</a></h4>
+<p>If true the consumer's offset will be periodically committed in the background.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="exclude.internal.topics"></a><a id="consumerconfigs_exclude.internal.topics" href="#consumerconfigs_exclude.internal.topics">exclude.internal.topics</a></h4>
+<p>Whether internal topics matching a subscribed pattern should be excluded from the subscription. It is always possible to explicitly subscribe to an internal topic.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="fetch.max.bytes"></a><a id="consumerconfigs_fetch.max.bytes" href="#consumerconfigs_fetch.max.bytes">fetch.max.bytes</a></h4>
+<p>The maximum amount of data the server should return for a fetch request. Records are fetched in batches by the consumer, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that the consumer can make progress. As such, this is not a absolute maximum. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.b [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>52428800 (50 mebibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="group.instance.id"></a><a id="consumerconfigs_group.instance.id" href="#consumerconfigs_group.instance.id">group.instance.id</a></h4>
+<p>A unique identifier of the consumer instance provided by the end user. Only non-empty strings are permitted. If set, the consumer is treated as a static member, which means that only one instance with this ID is allowed in the consumer group at any time. This can be used in combination with a larger session timeout to avoid group rebalances caused by transient unavailability (e.g. process restarts). If not set, the consumer will join the group as a dynamic member, which is the traditi [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td>non-empty string</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="group.remote.assignor"></a><a id="consumerconfigs_group.remote.assignor" href="#consumerconfigs_group.remote.assignor">group.remote.assignor</a></h4>
+<p>The name of the server-side assignor to use. If not specified, the group coordinator will pick the first assignor defined in the broker config group.consumer.assignors.This configuration is applied only if <code>group.protocol</code> is set to "consumer".</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="isolation.level"></a><a id="consumerconfigs_isolation.level" href="#consumerconfigs_isolation.level">isolation.level</a></h4>
+<p>Controls how to read messages written transactionally. If set to <code>read_committed</code>, consumer.poll() will only return transactional messages which have been committed. If set to <code>read_uncommitted</code> (the default), consumer.poll() will return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned unconditionally in either mode. <p>Messages will always be returned in offset order. Hence, in <code>read_committed</ [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>read_uncommitted</td></tr>
+<tr><th>Valid Values:</th><td>[read_committed, read_uncommitted]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="max.poll.interval.ms"></a><a id="consumerconfigs_max.poll.interval.ms" href="#consumerconfigs_max.poll.interval.ms">max.poll.interval.ms</a></h4>
+<p>The maximum delay between invocations of poll() when using consumer group management. This places an upper bound on the amount of time that the consumer can be idle before fetching more records. If poll() is not called before expiration of this timeout, then the consumer is considered failed and the group will rebalance in order to reassign the partitions to another member. For consumers using a non-null <code>group.instance.id</code> which reach this timeout, partitions will not be i [...]
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="max.poll.records"></a><a id="consumerconfigs_max.poll.records" href="#consumerconfigs_max.poll.records">max.poll.records</a></h4>
+<p>The maximum number of records returned in a single call to poll(). Note, that <code>max.poll.records</code> does not impact the underlying fetching behavior. The consumer will cache the records from each fetch request and returns them incrementally from each poll.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>500</td></tr>
+<tr><th>Valid Values:</th><td>[1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="partition.assignment.strategy"></a><a id="consumerconfigs_partition.assignment.strategy" href="#consumerconfigs_partition.assignment.strategy">partition.assignment.strategy</a></h4>
+<p>A list of class names or class types, ordered by preference, of supported partition assignment strategies that the client will use to distribute partition ownership amongst consumer instances when group management is used. Available options are:<ul><li><code>org.apache.kafka.clients.consumer.RangeAssignor</code>: Assigns partitions on a per-topic basis.</li><li><code>org.apache.kafka.clients.consumer.RoundRobinAssignor</code>: Assigns partitions to consumers in a round-robin fashion.< [...]
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>class org.apache.kafka.clients.consumer.RangeAssignor,class org.apache.kafka.clients.consumer.CooperativeStickyAssignor</td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="receive.buffer.bytes"></a><a id="consumerconfigs_receive.buffer.bytes" href="#consumerconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
+<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>65536 (64 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="request.timeout.ms"></a><a id="consumerconfigs_request.timeout.ms" href="#consumerconfigs_request.timeout.ms">request.timeout.ms</a></h4>
+<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.client.callback.handler.class"></a><a id="consumerconfigs_sasl.client.callback.handler.class" href="#consumerconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.jaas.config"></a><a id="consumerconfigs_sasl.jaas.config" href="#consumerconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
+<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.service.name"></a><a id="consumerconfigs_sasl.kerberos.service.name" href="#consumerconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
+<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.callback.handler.class"></a><a id="consumerconfigs_sasl.login.callback.handler.class" href="#consumerconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
+<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.class"></a><a id="consumerconfigs_sasl.login.class" href="#consumerconfigs_sasl.login.class">sasl.login.class</a></h4>
+<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.mechanism"></a><a id="consumerconfigs_sasl.mechanism" href="#consumerconfigs_sasl.mechanism">sasl.mechanism</a></h4>
+<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>GSSAPI</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.algorithm" href="#consumerconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
+<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>RS256</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.aud" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
+<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.iss" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
+<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
+<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>false</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.sub" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
+<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.file" href="#consumerconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
+<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.private.key.file" href="#consumerconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
+<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#consumerconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
+<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.template.file" href="#consumerconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
+<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="consumerconfigs_sasl.oauthbearer.client.credentials.client.id" href="#consumerconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
+<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="consumerconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#consumerconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
+<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
+<table><tbody>
+<tr><th>Type:</th><td>password</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="consumerconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#consumerconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
+<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="consumerconfigs_sasl.oauthbearer.jwt.retriever.class" href="#consumerconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="consumerconfigs_sasl.oauthbearer.jwt.validator.class" href="#consumerconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
+<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
+<table><tbody>
+<tr><th>Type:</th><td>class</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.scope"></a><a id="consumerconfigs_sasl.oauthbearer.scope" href="#consumerconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
+<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="consumerconfigs_sasl.oauthbearer.token.endpoint.url" href="#consumerconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
+<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="security.protocol"></a><a id="consumerconfigs_security.protocol" href="#consumerconfigs_security.protocol">security.protocol</a></h4>
+<p>Protocol used to communicate with brokers.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>PLAINTEXT</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="send.buffer.bytes"></a><a id="consumerconfigs_send.buffer.bytes" href="#consumerconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
+<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
+<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="share.acknowledgement.mode"></a><a id="consumerconfigs_share.acknowledgement.mode" href="#consumerconfigs_share.acknowledgement.mode">share.acknowledgement.mode</a></h4>
+<p>Controls the acknowledgement mode for a share consumer. If set to <code>implicit</code>, the acknowledgement mode of the consumer is implicit and it must not use <code>org.apache.kafka.clients.consumer.ShareConsumer.acknowledge()</code> to acknowledge delivery of records. Instead, delivery is acknowledged implicitly on the next call to poll or commit. If set to <code>explicit</code>, the acknowledgement mode of the consumer is explicit and it must use <code>org.apache.kafka.clients.co [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>implicit</td></tr>
+<tr><th>Valid Values:</th><td>[implicit, explicit]</td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="consumerconfigs_socket.connection.setup.timeout.max.ms" href="#consumerconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
+<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="socket.connection.setup.timeout.ms"></a><a id="consumerconfigs_socket.connection.setup.timeout.ms" href="#consumerconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
+<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.enabled.protocols"></a><a id="consumerconfigs_ssl.enabled.protocols" href="#consumerconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
+<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. Also see the config documentation for `ssl.protocol` to understand how it can impact the TLS version negotiation behavior.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.keystore.type"></a><a id="consumerconfigs_ssl.keystore.type" href="#consumerconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
+<p>The file format of the key store file. This is optional for client. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.protocol"></a><a id="consumerconfigs_ssl.protocol" href="#consumerconfigs_ssl.protocol">ssl.protocol</a></h4>
+<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in `ssl.enabled [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>TLSv1.3</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.provider"></a><a id="consumerconfigs_ssl.provider" href="#consumerconfigs_ssl.provider">ssl.provider</a></h4>
+<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="ssl.truststore.type"></a><a id="consumerconfigs_ssl.truststore.type" href="#consumerconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
+<p>The file format of the trust store file. The values currently supported by the default `ssl.engine.factory.class` are [JKS, PKCS12, PEM].</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>JKS</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>medium</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="auto.commit.interval.ms"></a><a id="consumerconfigs_auto.commit.interval.ms" href="#consumerconfigs_auto.commit.interval.ms">auto.commit.interval.ms</a></h4>
+<p>The frequency in milliseconds that the consumer offsets are auto-committed to Kafka if <code>enable.auto.commit</code> is set to <code>true</code>.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="check.crcs"></a><a id="consumerconfigs_check.crcs" href="#consumerconfigs_check.crcs">check.crcs</a></h4>
+<p>Automatically check the CRC32 of the records consumed. This ensures no on-the-wire or on-disk corruption to the messages occurred. This check adds some overhead, so it may be disabled in cases seeking extreme performance.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.id"></a><a id="consumerconfigs_client.id" href="#consumerconfigs_client.id">client.id</a></h4>
+<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="client.rack"></a><a id="consumerconfigs_client.rack" href="#consumerconfigs_client.rack">client.rack</a></h4>
+<p>A rack identifier for this client. This can be any string value which indicates where this client is physically located. It corresponds with the broker config 'broker.rack'</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="enable.metrics.push"></a><a id="consumerconfigs_enable.metrics.push" href="#consumerconfigs_enable.metrics.push">enable.metrics.push</a></h4>
+<p>Whether to enable pushing of client metrics to the cluster, if the cluster has a client metrics subscription which matches this client.</p>
+<table><tbody>
+<tr><th>Type:</th><td>boolean</td></tr>
+<tr><th>Default:</th><td>true</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="fetch.max.wait.ms"></a><a id="consumerconfigs_fetch.max.wait.ms" href="#consumerconfigs_fetch.max.wait.ms">fetch.max.wait.ms</a></h4>
+<p>The maximum amount of time the server will block before answering the fetch request there isn't sufficient data to immediately satisfy the requirement given by fetch.min.bytes. This config is used only for local log fetch. To tune the remote fetch maximum wait time, please refer to 'remote.fetch.max.wait.ms' broker config</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>500</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="interceptor.classes"></a><a id="consumerconfigs_interceptor.classes" href="#consumerconfigs_interceptor.classes">interceptor.classes</a></h4>
+<p>A list of classes to use as interceptors. Implementing the <code>org.apache.kafka.clients.consumer.ConsumerInterceptor</code> interface allows you to intercept (and possibly mutate) records received by the consumer. By default, there are no interceptors.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>""</td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.max.age.ms"></a><a id="consumerconfigs_metadata.max.age.ms" href="#consumerconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
+<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="consumerconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#consumerconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
+<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metadata.recovery.strategy"></a><a id="consumerconfigs_metadata.recovery.strategy" href="#consumerconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
+<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>rebootstrap</td></tr>
+<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metric.reporters"></a><a id="consumerconfigs_metric.reporters" href="#consumerconfigs_metric.reporters">metric.reporters</a></h4>
+<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
+<table><tbody>
+<tr><th>Type:</th><td>list</td></tr>
+<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
+<tr><th>Valid Values:</th><td>non-null string</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.num.samples"></a><a id="consumerconfigs_metrics.num.samples" href="#consumerconfigs_metrics.num.samples">metrics.num.samples</a></h4>
+<p>The number of samples maintained to compute metrics.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>2</td></tr>
+<tr><th>Valid Values:</th><td>[1,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.recording.level"></a><a id="consumerconfigs_metrics.recording.level" href="#consumerconfigs_metrics.recording.level">metrics.recording.level</a></h4>
+<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>INFO</td></tr>
+<tr><th>Valid Values:</th><td>[INFO, DEBUG, TRACE]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="metrics.sample.window.ms"></a><a id="consumerconfigs_metrics.sample.window.ms" href="#consumerconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
+<p>The window of time a metrics sample is computed over.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.max.ms"></a><a id="consumerconfigs_reconnect.backoff.max.ms" href="#consumerconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="reconnect.backoff.ms"></a><a id="consumerconfigs_reconnect.backoff.ms" href="#consumerconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
+<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>50</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.max.ms"></a><a id="consumerconfigs_retry.backoff.max.ms" href="#consumerconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
+<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>1000 (1 second)</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="retry.backoff.ms"></a><a id="consumerconfigs_retry.backoff.ms" href="#consumerconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
+<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>100</td></tr>
+<tr><th>Valid Values:</th><td>[0,...]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="consumerconfigs_sasl.kerberos.kinit.cmd" href="#consumerconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
+<p>Kerberos kinit command path.</p>
+<table><tbody>
+<tr><th>Type:</th><td>string</td></tr>
+<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="consumerconfigs_sasl.kerberos.min.time.before.relogin" href="#consumerconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
+<p>Login thread sleep time between refresh attempts.</p>
+<table><tbody>
+<tr><th>Type:</th><td>long</td></tr>
+<tr><th>Default:</th><td>60000</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="consumerconfigs_sasl.kerberos.ticket.renew.jitter" href="#consumerconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
+<p>Percentage of random jitter added to the renewal time.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.05</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="consumerconfigs_sasl.kerberos.ticket.renew.window.factor" href="#consumerconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
+<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.connect.timeout.ms"></a><a id="consumerconfigs_sasl.login.connect.timeout.ms" href="#consumerconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.read.timeout.ms"></a><a id="consumerconfigs_sasl.login.read.timeout.ms" href="#consumerconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
+<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>int</td></tr>
+<tr><th>Default:</th><td>null</td></tr>
+<tr><th>Valid Values:</th><td></td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="consumerconfigs_sasl.login.refresh.buffer.seconds" href="#consumerconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
+<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>300</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="consumerconfigs_sasl.login.refresh.min.period.seconds" href="#consumerconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
+<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>short</td></tr>
+<tr><th>Default:</th><td>60</td></tr>
+<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
+</tbody></table>
+</li>
+<li>
+<h4><a id="sasl.login.refresh.window.factor"></a><a id="consumerconfigs_sasl.login.refresh.window.factor" href="#consumerconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
+<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
+<table><tbody>
+<tr><th>Type:</th><td>double</td></tr>
+<tr><th>Default:</th><td>0.8</td></tr>
+<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
+<tr><th>Importance:</th><td>low</td></tr>
... 367735 lines suppressed ...