Skip to content

[Feature] Import Wizard for Installation Setup #586

Closed
1 of 1 issue completed
Closed

Description

@JinkunLiu

Motivation

Enhance the quickstart experience. - Currently, there are too many manual steps, thus chances for users to make mistakes and run into problems.

Installation Flow

1) Ask user whether to install Flink

If user selects Yes:

  • Download the Flink binary archive to a temporary directory.
  • Extract Flink into the target installation directory and remove the downloaded archive.
  • Set and export FLINK_HOME.

If user selects No:

  • Validate that FLINK_HOME is already set and points to a valid Flink directory .

2) Ask user whether to enable PyFlink

If user selects Yes:

  • Copy flink-python JAR from $FLINK_HOME/opt/ to $FLINK_HOME/lib/.
  • Create and activate a Python virtual environment.
  • Install flink-agents and pinned apache-flink via pip.
  • Copy Flink Agents Java artifacts into $FLINK_HOME/lib/.

If user selects No:

  • Skip all Python/PyFlink-related steps.

Are you willing to submit a PR?

  • I'm willing to submit a PR!

Activity

  1. added
    feature[Issue Type] New features or improvements to existing features.
    priority/majorDefault priority of the PR or issue.
    on Mar 25, 2026
  2. wenjin272 commented on May 22, 2026

    @wenjin272
    Contributor

    Hi, @JinkunLiu, Ty for contributing the install script.

    The code pr has been merged, but before we close this issue, I think we need refactor the installation documentation for flink-agents. I have created sub-issue #699 for this. Are you interested in taking this issue?

  3. JinkunLiu commented on May 22, 2026

    @JinkunLiu
    ContributorAuthor

    Hi @wenjin272, Thanks for your help in getting this issue done together, and thanks for setting up the follow-up sub-issue!

    I'd be glad to take on #699. Please feel free to assign it to me. I'll provide a refactored documentation outline as soon as possible so we can align on the structure first.

  4. added
    fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.
    and removed
    fixVersion/missingThe Bot applies this label when fixVersion is not set.
    on Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

affectVersion/0.3.0feature[Issue Type] New features or improvements to existing features.fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.priority/majorDefault priority of the PR or issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions