Feature Request: Custom listener_name for Functions
- 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
The motivation of this feature comes from: #21088
To be more specific from [this comment](https://github.com/apache/pulsar/issues/21088#issuecomment-1717797667).
Currently, when creating a function worker / sink / source one can assign a custom `broker-service-url` but not a `listener_name` usable through the brokers `advertisedListeners`, hence preventing running workers on dedicated machines outside of the brokers network (as far as I'm aware of).
### Solution
Enable function workers / sinks / sources to be created with a custom `--listener_name` flag used by the client.
### 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
The issue names no files or tests. Start by locating the function worker, sink, and source creation paths and the existing broker-service-url option; trace how client settings are passed, then verify that a custom listener_name is accepted and used with advertisedListeners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100