Hi Team,
I am currently reviewing how Nussknacker handles the deployment of job scenarios in Flink.
Based on my understanding, when a user selects Deploy, Nussknacker uploads the required JAR files to the Flink JobManager. Along with the JAR, the DAG of the scenario is also passed. Subsequently, the Flink REST API is used to submit the job, executing the JAR with the DAG as an argument.
Kindly confirm if my understanding is correct. If not, I would appreciate it if you could explain how these JAR files function internally and how they are transformed into a Flink pipeline.
Thank you for your support.
--
You received this message because you are subscribed to the Google Groups "Nussknacker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nussknacker...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/nussknacker/4fa4983c-1b2b-49c9-b0a2-b78d4d5e1f94n%40googlegroups.com.