[ 
https://issues.apache.org/jira/browse/FLINK-10494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638969#comment-16638969
 ] 

ASF GitHub Bot commented on FLINK-10494:
----------------------------------------

isunjin opened a new pull request #6794: [FLINK-10494] [Job Manager] Rename 
'JobManager' to 'JobMaster' for some classes in JobMaster folder
URL: https://github.com/apache/flink/pull/6794
 
 
   
   ## What is the purpose of the change
   
   * this pull request is a code renaming, no logic change
   
   ## Brief change log
     - *rename JobManagerRunner -> JobMasterRunner*
     - *JobManagerSharedServices -> JobMasterSharedServices*
     - *delete JobManagerException as it duplicate with JobMasterException*
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)

Reply via email to