merlimat opened a new pull request, #25639:
URL: https://github.com/apache/pulsar/pull/25639
## Summary
Follow-up to #25632. Replaces the single `(propertyKey, propertyValue)`
filter on the scalable-topic listing API with a `Map<String, String>` of
filters that all must match (AND semantics). Empty map degenerates to the
unfiltered listing.
### Resources
- `ScalableTopicResources.findScalableTopicsByPropertiesAsync(ns,
Map<String, String>)`
picks any single filter to drive the index lookup (native stores narrow
on it; fallback stores scan), then post-filters with an "all properties
match" predicate. The post-filter runs both inside `findByIndex` (for
fallback stores) and in the result-mapping stage, because native-index
implementations don't apply `fallbackFilter` — on the fallback path the
re-check is a no-op.
### Admin API
- `GET /admin/v2/scalable/{tenant}/{ns}` now takes repeatable
`?property=key=value` query params instead of paired `propertyKey` /
`propertyValue`. Malformed entries (no `=`, empty key, empty value) fail
with 412.
- `ScalableTopics` admin client renames the API to
`listScalableTopicsByProperties(ns, Map<String, String>)`. The client
serialises every entry as a separate `?property=k=v` parameter.
- `pulsar-admin scalable-topics list -p k1=v1 -p k2=v2 ...` accepts
multiple `--property` options; same key=value parsing as the matching
`create` subcommand.
## Test plan
- Existing `ScalableTopicPropertyIndexTest` updated to use the new
signature; gains an AND-semantics case (`owner=alice AND team=platform`
narrows to a single record even though either filter alone matches more)
and an empty-filter case (returns full namespace listing).
- `ScalableTopicsListByPropertyTest` end-to-end test exercises the same
multi-filter combo through `PulsarAdmin`.
### Matching PR(s) in forked repositories
- area/broker
- area/client-tools
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
