-
Notifications
You must be signed in to change notification settings - Fork 14.9k
KAFKA-19590: Add prefix to TopicBasedRemoteLogMetadataManagerConfig to enable setting admin configs #21277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…o enable setting admin configs
# Conflicts: # docs/configuration.html
chia7712
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DL1231 thanks for this patch
...pache/kafka/server/log/remote/metadata/storage/TopicBasedRemoteLogMetadataManagerConfig.java
Outdated
Show resolved
Hide resolved
frankvicky
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
|
||
| private Map<String, Object> createAdminProps(Map<String, Object> allAdminConfigs) { | ||
| Map<String, Object> props = new HashMap<>(allAdminConfigs); | ||
| props.put(ProducerConfig.CLIENT_ID_CONFIG, clientIdPrefix + "_admin"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ProducerConfig -> AdminClientConfig
Currently,
TopicBasedRemoteLogMetadataManagercreates the Admin clientusing
commonProperties(), which prevents users from settingadmin-specific configurations (e.g., custom timeouts, retry policies).
This commit adds a new configuration prefix
remote.log.metadata.admin.*to allow separate configuration for theAdmin client, similar to the existing producer and consumer prefixes.
Reviewers: TengYao Chi frankvicky@apache.org, Chia-Ping Tsai
chia7712@gmail.com