GitHub user zjureel opened a pull request:
https://github.com/apache/flink/pull/4475
[FLINK-7251] Add proper command line parsing tool to ClusterEntrypoint
## What is the purpose of the change
Add a proper command line parsing tool `CommandLineParser` to the entry
point of the ClusterEntrypoint#parseArguments
## Brief change log
- *Add command line parsing tool `CommandLineParser`*
- *Use `CommandLineParser` instead of `ParameterTool` in
ClusterEntrypoint#parseArguments*
## Verifying this change
*(Please pick either of the following options)*
This change added tests and can be verified as follows:
*(example:)*
- *Added test case `CommandLineParserTest`*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable / docs /
JavaDocs / not documented)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjureel/flink FLINK-7307
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4475.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 #4475
----
commit 7f0e67daf9f66d68201b9e660a3ba8328fad2ce2
Author: zjureel <[email protected]>
Date: 2017-08-04T08:08:05Z
[FLINK-7251][improvement] Add proper command line parsing tool to
ClusterEntrypoint
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
