improve doc

Author: coderzc

pip/pip-452.md

@@ -18,6 +18,8 @@ Broker: Extend `BrokerInterceptor` to allow plugins to intercept the "Get Topics
 
 Client: Update the Java Client to forward Consumer properties to the lookup service when using Regex subscriptions.
 
+Admin API & CLI: Update the REST API and CLI to accept properties for listing topics in a namespace.
+
 # High Level Design
 We will modify the Pulsar Protocol to carry a properties map. On the Broker side, we will add a new method to the BrokerInterceptor interface.
 The default implementation will preserve the existing behavior (fetching from ZooKeeper). The Broker's connection handler will simply delegate the request to this strategy.
@@ -49,9 +51,9 @@ message CommandGetTopicsOfNamespace {
 
 Add `properties` parameter to the REST API endpoint for listing topics in a namespace to list topic with specific properties for customizable topic listing.
 
-REST API:
+REST API (URL encoding is required for values):
 ```
-GET /admin/v2/persistent/{tenant}/{namespace} with a query params properties=k1=v1,k2=v2
+GET /admin/v2/persistent/{tenant}/{namespace}?properties=k1=v1,k2=v2
 ```
 
 CLI:
@@ -212,14 +214,15 @@ The regex consumer implementation (PatternMultiTopicsConsumerImpl) will be updat
 
 ```Java
 // In PatternMultiTopicsConsumerImpl.java
+ConsumerConfigurationData conf;
 Map<String, String> contextProperties = conf.getProperties();
 
 lookup.getTopicsUnderNamespace(
     namespace, 
     mode, 
     topicsPattern.pattern(), 
     topicsHash, 
-    contextProperties // Pass properties here
+    contextProperties // Pass consumer properties here
 ).thenAccept(topics -> {
     // ... update subscriptions ...
 });
@@ -238,5 +241,5 @@ Authorization: This PIP only controls the discovery (listing) of topics. It does
 
 # Links
 
-* Mailing List discussion thread:
+* Mailing List discussion thread: https://lists.apache.org/thread/nf11qzn6r9wps6l81trxwtdr1m9xszpm
 * Mailing List voting thread: