[
https://issues.apache.org/jira/browse/KAFKA-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113990#comment-18113990
]
ASF GitHub Bot commented on KAFKA-21018:
----------------------------------------
chia7712 commented on code in PR #909:
URL: https://github.com/apache/kafka-site/pull/909#discussion_r3982729354
##########
content/en/43/getting-started/upgrade.md:
##########
@@ -140,7 +140,7 @@ For further details, please refer to
[KIP-1120](https://cwiki.apache.org/conflue
* The metrics
`org.apache.kafka.server:type=AssignmentsManager.QueuedReplicaToDirAssignments`,
`org.apache.kafka.storage.internals.log:type=RemoteStorageThreadPool.RemoteLogReaderTaskQueueSize`,
and
`org.apache.kafka.storage.internals.log:type=RemoteStorageThreadPool.RemoteLogReaderAvgIdlePercent`
have been deprecated and will be removed in Kafka 5.0. As replacements, the
following metrics have been introduced, which report the same information:
`kafka.server:type=AssignmentsManager.QueuedReplicaToDirAssignments`,
`kafka.log.remote:type=RemoteStorageThreadPool.RemoteLogReaderTaskQueueSize`,
and
`kafka.log.remote:type=RemoteStorageThreadPool.RemoteLogReaderAvgIdlePercent`.
For further details, please refer to
[KIP-1100](https://cwiki.apache.org/confluence/x/6oqMEw).
* A new metric `AvgIdleRatio` has been added to the `ControllerEventManager`
and `MetadataLoader` groups. These metrics measure the average idle ratio of
their respective event queue threads, providing visibility into how much time
each component spends waiting for events versus processing them. The metric
value ranges from 0.0 (always busy) to 1.0 (always idle).
* Deprecated `org.apache.kafka.streams.KafkaStreams$CloseOptions` and its
related methods, such as
`KafkaStreams#close(org.apache.kafka.streams.KafkaStreams$CloseOptions)`. As a
replacement, please use `org.apache.kafka.streams.CloseOptions` and
`KafkaStreams#close(org.apache.kafka.streams.CloseOptions)`. For further
details, please refer to
[KIP-1153](https://cwiki.apache.org/confluence/x/QAq9F).
- * A new implementation of `ConnectorClientConfigOverridePolicy`,
`AllowlistConnectorClientConfigOverridePolicy`, has been added. This enables
specifying the configurations that connectors can override via
`connector.client.config.override.allowlist`. From Kafka 5.0.0, this will be
the default
[connector.client.config.override.policy](documentation/#connectconfigs_connector.client.config.override.policy)
policy. The `PrincipalConnectorClientConfigOverridePolicy` policy is now
deprecated and will be removed in Kafka 5.0.0. For further details, please
refer to [KIP-1188](https://cwiki.apache.org/confluence/x/2IkvFg).
+* A new implementation of `ConnectorClientConfigOverridePolicy`,
`AllowlistConnectorClientConfigOverridePolicy`, has been added. This enables
specifying the configurations that connectors can override via
`connector.client.config.override.allowlist`. From Kafka 5.0.0, this will be
the default
[connector.client.config.override.policy](/{version}/configuration/kafka-connect-configs/#connectconfigs_connector.client.config.override.policy)
policy. The `PrincipalConnectorClientConfigOverridePolicy` policy is now
deprecated and will be removed in Kafka 5.0.0. For further details, please
refer to [KIP-1188](https://cwiki.apache.org/confluence/x/2IkvFg).
Review Comment:
This file is copied from the kafka repo by the RM when releasing, so we
don't need to update it here
> Broken links in Kafka docs and javadocs
> ---------------------------------------
>
> Key: KAFKA-21018
> URL: https://issues.apache.org/jira/browse/KAFKA-21018
> Project: Kafka
> Issue Type: Bug
> Components: documentation
> Reporter: Gergely Harmadás
> Assignee: Gergely Harmadás
> Priority: Minor
>
> I have found a few instances of broken links in the Kafka codebase:
> * plugindiscovery
> **
> [https://github.com/apache/kafka/blob/f35c72c5deefd9c18a66ba2fb2ea2cf37e9a76c5/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/isolation/Plugins.java#L121]
> * connect_exactlyoncesource
> **
> [https://github.com/apache/kafka/blob/4db407403335427ffa22323190eeff2aa63c3ccd/docs/operations/geo-replication-(cross-cluster-data-mirroring).md?plain=1#L192]
> **
> [https://github.com/apache/kafka/blob/1807f7e846e9ffb2293d3b7eb855ce088f70c9a6/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedConfig.java#L266]
> * upgrade_240_notable
> **
> [https://github.com/apache/kafka/blob/fac6838045e8de367666730d8f12b434596eb71c/clients/src/main/java/org/apache/kafka/clients/consumer/CooperativeStickyAssignor.java#L51]
> * connectconfigs_connector.client.config.override.policy
> **
> [https://github.com/apache/kafka/blob/a5b195269314cec9549416d86094eac95aa1d79d/docs/getting-started/upgrade.md?plain=1#L165]
> Fixing some of these also requires changes in kafka-site
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
