The benefit of the ParameterTool is that you do not increase your
dependency footprint by using it.
When using another CLI library you will generally package it within your
user-jar, which may or may not increase the risk of dependency conflicts.
Whether, and how large this risk is, depends naturally on the library.
This also results in a larger jar file, which may or may not be relevant
for you.
On 11/08/2020 23:35, Marco Villalobos wrote:
Thank you for the clarification.
But does it offer any additional benefits that are not clearly documented?
On Tue, Aug 11, 2020 at 12:22 PM Robert Metzger <rmetz...@apache.org
<mailto:rmetz...@apache.org>> wrote:
Hi,
there are absolutely no dangers not using ParameterTool.
It is used by the Flink examples, and as a showcase for global job
parameters:
https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/best_practices.html#register-the-parameters-globally
On Tue, Aug 11, 2020 at 7:13 PM Marco Villalobos
<mvillalo...@kineteque.com <mailto:mvillalo...@kineteque.com>> wrote:
What are the dangers of not using the ParameterTool for
parsing command line parameters?
I have been using Picocli (https://picocli.info/). Will this
be a mistake? Are there any side-effects that I should be
aware of?
