-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed as not planned
Closed as not planned
Copy link
Labels
lifecycle/staletype/enhancementThe enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messagesThe enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Description
Is your enhancement request related to a problem? Please describe.
When specifying resources in either function worker configuration (min/max/...) or function APIs (creation), the specified value must be an explicit number, just as the official example shows:
$ bin/pulsar-admin functions create \
--jar target/my-functions.jar \
--classname org.example.functions.MyFunction \
--cpu 8 \
--ram 8589934592 \
--disk 10737418240Especially for the storage which could be a large number, it's tedious and error-prone to specify these values as decimals explicitly.
Describe the solution you'd like
Maybe pulsar could take the example of the pattern of how Kubernetes define the value of resources:
- 12Mi: 12 * (2 ^ 20)
- 12M: 12 * (10 ^ 6)
- 1000m: 1 cpu
Describe alternatives you've considered
Maybe the storage quantity should be prioritized.
Additional context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
lifecycle/staletype/enhancementThe enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messagesThe enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages