Hi, Yes, I think it’s a good idea to make the options uniform. Using ‘#’ as a separator for options that take two values seems a bit strange to me, did you research if any other CLI tools have this convention?
Side note: I don’t like that our options use camel-case, I think that’s very non-standard. But that’s how it is now… Best, Aljoscha > On 3. Dec 2019, at 10:14, jincheng sun <sunjincheng...@gmail.com> wrote: > > Thanks for bringup this discussion Wei! > I think this is very important for Flink User, we should contains this > changes in Flink 1.10. > +1 for the optimization from the perspective of user convenience and the > unified use of Flink command line parameters. > > Best, > Jincheng > > Wei Zhong <weizhong0...@gmail.com> 于2019年12月2日周一 下午3:26写道： > >> Hi everyone, >> >> I wanted to bring up the discussion of improving the Pyflink command line >> options. >> >> A few command line options have been introduced in the FLIP-78 [1], i.e. >> "python-executable-path", "python-requirements","python-archive", etc. >> There are a few problems with these options, i.e. the naming style, >> variable argument options, etc. >> >> We want to make some adjustment of FLIP-78 to improve the newly introduced >> command line options, here is the design doc: >> >> https://docs.google.com/document/d/1R8CaDa3908V1SnTxBkTBzeisWqBF40NAYYjfRl680eg/edit?usp=sharing >> < >> https://docs.google.com/document/d/1R8CaDa3908V1SnTxBkTBzeisWqBF40NAYYjfRl680eg/edit?usp=sharing >>> >> Looking forward to your feedback! >> >> Best, >> Wei >> >> [1] >> https://cwiki.apache.org/confluence/display/FLINK/FLIP-78%3A+Flink+Python+UDF+Environment+and+Dependency+Management >> < >> https://cwiki.apache.org/confluence/display/FLINK/FLIP-78:+Flink+Python+UDF+Environment+and+Dependency+Management >>> >> >>
