wenjin272 commented on PR #599: URL: https://github.com/apache/flink-agents/pull/599#issuecomment-4324018552
Hi, @JinkunLiu, thanks for your update. Since flink-agents provides multi-version support, and considering that some developers' clusters may not yet be compatible with the latest Flink version, I believe it might be too inflexible to always download the latest Flink version. > Now the install shell provides the latest version as default. Users can use all the features we provide in the latest version.If they need special version about Flink or Flink-agents they can use cli flag. This is what I mean when I say that users need to understand many CLI flags. Why can't users be allowed to select a specific Flink version, rather than being required to specify it via a CLI flag? We provide a GUI-like installation wizard, but users are still required to manually specify certain cli flag to achieve specific goals. I believe this creates a fragmented user experience. I think for some less frequent requirements, such as dry-run and verbose, we can simply only provide CLI flags. However, for some high-frequency requirements, I believe it would be a more user-friendly experience to allow users to select options during the installation guide, rather than requiring them to read and understand the information returned by help and setting CLI flags or environment variables. I think these requirements contains: 1. intall dir: we can provide two options: default vs. custom, and if user choose custom, they need input the custom dir. 2. install flink: yes vs. no, and check the FLINK_HOME when user choose no. 3. flink-version: 4 options, 1.20.3, 2.0.1, 2.1.1, 2.2.0(recommend) 4. install pyflink: yes vs. no After the user makes the above selections, we will then output the Install Plan. Additionally, when running the script on my Mac, I encountered the error die: command not found. You may need to replace it with a more universally available command. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
