[ https://issues.apache.org/jira/browse/SPARK-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reynold Xin updated SPARK-15518: -------------------------------- Description: Various scheduler backends are not named consistently, making it difficult to understand what they do based on the names. It would be great to rename some of them: - LocalScheduler -> LocalSchedulerBackend - AppClient -> StandaloneAppClient - AppClientListener -> StandaloneAppClientListener - SparkDeploySchedulerBackend -> StandaloneSchedulerBackend - CoarseMesosSchedulerBackend -> MesosCoarseGrainedSchedulerBackend - MesosSchedulerBackend -> MesosFineGrainedSchedulerBackend was: SparkDeploySchedulerBackend is a weird name and inconsistent with rest of the backends (e.g. CoarseMesosSchedulerBackend). > Rename various scheduler backend for consistency > ------------------------------------------------ > > Key: SPARK-15518 > URL: https://issues.apache.org/jira/browse/SPARK-15518 > Project: Spark > Issue Type: Sub-task > Components: Spark Core > Reporter: Reynold Xin > Assignee: Reynold Xin > > Various scheduler backends are not named consistently, making it difficult to > understand what they do based on the names. It would be great to rename some > of them: > - LocalScheduler -> LocalSchedulerBackend > - AppClient -> StandaloneAppClient > - AppClientListener -> StandaloneAppClientListener > - SparkDeploySchedulerBackend -> StandaloneSchedulerBackend > - CoarseMesosSchedulerBackend -> MesosCoarseGrainedSchedulerBackend > - MesosSchedulerBackend -> MesosFineGrainedSchedulerBackend -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org