[
https://issues.apache.org/jira/browse/FLINK-10494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640903#comment-16640903
]
Till Rohrmann commented on FLINK-10494:
---------------------------------------
Thanks for opening this issue [~isunjin]. It is true that the mixed naming is
quite confusing and unfortunate. The long term idea was to use the old and
established terminology for the new components. That way, the users don't have
to learn something new. This would mean that we rename JobMaster into
JobManager once we have remove the legacy code.
Since we are currently working on removing the legacy code, it might not be
necessary to first rename everything into JobMaster*. What do you think?
> Rename 'JobManager' to 'JobMaster' for some classes in JobMaster folder
> -----------------------------------------------------------------------
>
> Key: FLINK-10494
> URL: https://issues.apache.org/jira/browse/FLINK-10494
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager
> Affects Versions: 1.6.0, 1.7.0
> Reporter: JIN SUN
> Assignee: JIN SUN
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> Some names in
> "flink-runtime/src/main/java/org/apache/flink/runtime/jobmaster" folder are
> confusing, we should rename it to JobMaster.
>
> * JobManagerRunner -> JobMasterRunner
> * JobManagerGateway -> JobMasterGateway
> * JobManagerSharedServices -> JobMasterSharedServices
> * JobManagerException -> JobMasterException
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
