GitHub user hsaputra opened a pull request:

    https://github.com/apache/flink/pull/482

    Remove -j and -a parameters which seemed no longer valid in the doc example 
for YARN

    From:
    
    ./bin/flink run -j 
./examples/flink-java-examples-{{site.FLINK_VERSION_SHORT }}-WordCount.jar \
          -a 1 hdfs:///..../apache-license-v2.txt 
hdfs:///.../wordcount-result.txt
    
    To:
    
    ./bin/flink run ./examples/flink-java-examples-{{site.FLINK_VERSION_SHORT 
}}-WordCount.jar \
           hdfs:///..../apache-license-v2.txt hdfs:///.../wordcount-result.txt
    
    Looking at http://ci.apache.org/projects/flink/flink-docs-master/cli.html 
seemed like -j and -a are no longer valid?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hsaputra/flink fix_doc_run_onyarn_params

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/482.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #482
    
----
commit 1ae0c5779b0c8b64feb9fd5f00b51a9b83cd4e0e
Author: Henry Saputra <henry.sapu...@gmail.com>
Date:   2015-03-12T23:18:03Z

    Remove -j and -a parameters which seemed no longer valid in the doc example
    for submit job to Flink run in YARN.
    
    From:
    
    ./bin/flink run -j 
./examples/flink-java-examples-{{site.FLINK_VERSION_SHORT }}-WordCount.jar \
          -a 1 hdfs:///..../apache-license-v2.txt 
hdfs:///.../wordcount-result.txt
    
    To:
    
    ./bin/flink run ./examples/flink-java-examples-{{site.FLINK_VERSION_SHORT 
}}-WordCount.jar \
           hdfs:///..../apache-license-v2.txt hdfs:///.../wordcount-result.txt

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to