Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1035#issuecomment-133340112
Hi @gallenvara, great to see that more and more new people join the Flink
community :-)
IMHO, whether a method is used from within the same class or not is not a
good indicator for moving a method out of it. You'll find many classes in Flink
which define methods which are not used by itself. It's part of the idea of OOP
that the methods you define on a class constitute the interface to it. Thus, it
defines what you can do with it. In that sense, `makeQualified` should stay
part of the `Path` class, because it allows you to create a qualified path
object from another path object.
Moreover, scattering functionality around in some static util classes won't
make it easier for others to actually find it. How should people know that
there is a class `FileSystemUtil` which allows you to convert paths into
qualified paths? It's more natural to look at the methods defined in the `Path`
class. Having much code in one class is not per se bad if you structure it
clearly and if your methods don't become behemoths it's fine. I also don't
think that @fhueske had this in mind when he created the JIRA issue.
Maybe I'm totally wrong here, but I think we should close this PR.
---
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.
---
