Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
The only thing what the PortRange utility does is wrapping a NetUtils#getPortRangeFromString to help keeping track of the original config string.
Considering this, it makes sense to move it to the same module, as currently PortRange is in flink-runtime, which limits its usage to that module, or requiring to add it as a dependency, which is not a very good option.
Attachments
Issue Links
- is required by
-
FLINK-36240 Incorrect Port display in the PrometheusReporter constructor
- Resolved