Support custom properties for Tenants and Namespaces
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Motivation
In Pulsar 2.11 we can store custom properties in Topics and in Subscription.
We lack the ability to tag Tenants and Namespaces with custom properties.
### Solution
Support setting a custom set of key-value pairs on Tenants and on Namespaces.
The map can be immutable
### Alternatives
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by examining the existing custom-property support for topics and subscriptions, then trace how tenant and namespace settings are exposed and persisted. The work is done when both tenants and namespaces support setting key-value custom properties, including an immutable map if appropriate, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100