Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2226
Separating classes certainly makes navigation trickier, but should we
sacrifice code-stability (Preconditions/NetUtils) for it? I believe a
separation of interfaces and implementation is a good compromise; users can
write against the small flink-metrics-core jar, but we retain the ability to
use all utilities have.
If we want to move implementations into flink-metrics-core to make
navigation easier i would propose to move all classes there. Being able to use
JobID etc. directly is imo less of a benefit than the utilities.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
