Chesnay Schepler created FLINK-3666:
---------------------------------------

             Summary: Remove Nephele references
                 Key: FLINK-3666
                 URL: https://issues.apache.org/jira/browse/FLINK-3666
             Project: Flink
          Issue Type: Improvement
          Components: Documentation
            Reporter: Chesnay Schepler
            Priority: Trivial


There still exist a few references to nephele which should be removed:

{code}
flink\docs\setup\local_setup.md:
   79  $ tail log/flink-*-jobmanager-*.log
   80  INFO ... - Initializing memory manager with 409 megabytes of memory
   81: INFO ... - Trying to load 
org.apache.flinknephele.jobmanager.scheduler.local.LocalScheduler as scheduler
   82  INFO ... - Setting up web info server, using web-root directory ...
   83: INFO ... - Web info server will display information about nephele 
job-manager on localhost, port 8081.
   84  INFO ... - Starting web info server for JobManager on port 8081
   85  ~~~
   ..
  118  $ cd flink
  119  $ bin/start-local.sh
  120: Starting Nephele job manager
  121  ~~~
{code}

{code}
flink\flink-runtime\src\main\java\org\apache\flink\runtime\operators\TaskContext.java:
   70:  AbstractInvokable getOwningNepheleTask();
{code}

{code}
flink\flink-runtime\src\main\java\org\apache\flink\runtime\operators\BatchTask.java:
 1149    * @param message The main message for the log.
 1150    * @param taskName The name of the task.
 1151:   * @param parent The nephele task that contains the code producing the 
message.
 1152    *
 1153    * @return The string for logging.
 ....
 1254    */
 1255   @SuppressWarnings("unchecked")
 1256:  public static <T> Collector<T> initOutputs(AbstractInvokable 
nepheleTask, ClassLoader cl, TaskConfig config,
 1257                                                                           
List<ChainedDriver<?, ?>> chainedTasksTarget,
 1258                                                                           
List<RecordWriter<?>> eventualOutputs,
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to