GitHub user JinkunLiu added a comment to the discussion: [Feature] Enhance the 
quickstart experience

  Hello @xintongsong Thanks for your advice.
  
  About you question:

> Not entirely sure what you mean by "Flink's Quick Start". Flink's [First 
> Steps](https://nightlies.apache.org/flink/flink-docs-master/docs/getting-started/local_installation/)
>  provides three options, none of which uses the MiniCluster.

I think the [Flink-Agents docs 
Quickstart](https://nightlies.apache.org/flink/flink-agents-docs-main/docs/get-started/quickstart/workflow_agent/)
 is analogous to [Flink's Tutorial 
section](https://nightlies.apache.org/flink/flink-docs-master/docs/getting-started/table_api/).
 
Perhaps my earlier wording was a bit unclear — I only want to use mini cluster 
in the [Flink-Agents docs 
Quickstart](https://nightlies.apache.org/flink/flink-agents-docs-main/docs/get-started/quickstart/workflow_agent/)
 instead of a standalone cluster. I think move `Submit Flink Agents Job to 
Standalone Flink Cluster` to another location maybe is better?  But If you're 
concerned about submitting the Quickstart demo to the miniCluster, it's better 
to keep that.


> Alternatively, we can wait until the project becomes more stable. I've never 
> worked on an archetype, thus not sure how much effort that takes. WDYT?

I agree that we can do it later. In terms of development cost, I don't think 
the overall difficulty is high; however, iterating before things are stable 
might be a bit troublesome.


> about structure you offered

Yes, that structure looks better, but I wan to know whether you have more 
details about what the `Wizard part` should do?

GitHub link: 
https://github.com/apache/flink-agents/discussions/555#discussioncomment-15987236

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to