To me creating the PackagedProgram on the client side is very bad, at least
for 2 things:
1. You must ensure to have almost the same classpath of the Flink
cluster otherwise you can face problems in deserializing the submitted job
graph (for example jackson automatically tries to create modules
Actually, I think the key point is that the Flink client is not friendly to
the deployers.
Most companies have their own deployers and I believe many of them depend on
the cli commands(e.g. "flink run/run-application").
I am not sure whether using the rest cluster client is the best choice. But
we
I'm surprised that this is not possible currently. Seems like a glaring
missing feature to me.
I'd assume the best way would be to extend the REST API to /jar/:jarId/run
with an option to overwrite configuration values. I'm not sure how to map
json well to the yaml structure of the config, but I g
Hi Fabian,
thanks for starting this discussion. In general I would be a bit hesitant
to build upon Flink's web UI submission because it suffers from a couple of
drawbacks.
1) The web UI submission only supports single job applications.
2) The JobGraph is generated from within the web UI Netty thr
Hi all,
Currently, the most convenient way of programmatically submitting a job to a
running session cluster is using Flink’s RestClusterClient.
Unfortunately, it is only supported, as of now, to submit a job graph.[1] To
construct a job graph from a jar file, additional Flink dependencies are
