You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2023/06/13 09:53:00 UTC

[jira] [Created] (KAFKA-15083) Passing "remote.log.metadata.*" configs into RLMM

Luke Chen created KAFKA-15083:
---------------------------------

             Summary: Passing "remote.log.metadata.*" configs into RLMM
                 Key: KAFKA-15083
                 URL: https://issues.apache.org/jira/browse/KAFKA-15083
             Project: Kafka
          Issue Type: Sub-task
            Reporter: Luke Chen


Based on the [KIP-405|https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage#KIP405:KafkaTieredStorage-Configs]:
|_{color:#000000}remote.log.metadata.*{color}_|{color:#000000}Default RLMM implementation creates producer and consumer instances. Common client propoerties can be configured with `remote.log.metadata.common.client.` prefix.  User can also pass properties specific to {color}{color:#000000}producer/consumer with `remote.log.metadata.producer.` and `remote.log.metadata.consumer.` prefixes. These will override properties with `remote.log.metadata.common.client.` prefix.{color}
{color:#000000}Any other properties should be prefixed with "remote.log.metadata." and these will be passed to RemoteLogMetadataManager#configure(Map<String, ?> props).{color}
{color:#000000}For ex: Security configuration to connect to the local broker for the listener name configured are passed with props.{color}|

 

This is missed from current implementation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)