Enhance GetTopicsOfNamespace with customizable topic listing using properties

Author: coderzc

pip/pip-452.md

@@ -23,8 +23,11 @@ We will modify the Pulsar Protocol to carry a properties map. On the Broker side
 The default implementation will preserve the existing behavior (fetching from ZooKeeper). The Broker's connection handler will simply delegate the request to this strategy.
 
 # Detailed Design
-1. Protocol Changes
-We update `PulsarApi.proto` to include the properties field.
+
+## Public-facing Changes
+
+### Protocol Changes
+Update `PulsarApi.proto` to include the properties field.
 
 PulsarApi.proto
 ```protobuf
@@ -41,7 +44,23 @@ message CommandGetTopicsOfNamespace {
     repeated KeyValue properties = 6;
 }
 ```
-2. Broker Changes
+
+### REST API & CLI Changes
+
+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:
+```
+GET /admin/v2/persistent/{tenant}/{namespace} with a query params properties=k1=v1,k2=v2
+```
+
+CLI:
+```
+pulsar-admin topics list <tenant>/<namespace> -p k1=v1 -p k2=v2"
+```
+
+## Design & Implementation Details
+### Broker Changes
 
 Add `TopicListingResult` for listing topic results
 
@@ -239,7 +258,7 @@ private void internalHandleGetTopicsOfNamespace(String namespace, NamespaceName
 }
 ```
 
-3. Client Changes
+### Client Changes
 Update LookupService
 The internal LookupService interface is updated to accept the properties map.
 
@@ -269,6 +288,8 @@ lookup.getTopicsUnderNamespace(
     // ... update subscriptions ...
 });
 ```
+
+
 # Backward Compatibility
 Protocol: Adding an optional field (properties) to the Protobuf definition is non-breaking. Old clients will not send this field; old brokers will ignore it.