👋 - I’m looking into running custom

FlinkSessionJob

deployments, and am trying to figure out which image is used to run these jobs. For example, I followed the instructions to run the

flink-sql-runner-example

JAR here. This example works when defining the job under a

FlinkDeployment

definition. However, if I convert this job to a

FlinkSessionJob

definition, I get a

FileNotFoundException

thrown when attempting to find the JAR file on the local file system, which leads me to believe session jobs are not using the image defined by my deployment. Are session jobs using the operator image?

What jarURI are you setting when running it via FlinkDeployment? I have also seen this when passing a jar file path for the local Filesystem. Say if I give jarURI: file:///some-dir/my-jar.jar, then the operator expects that this jar exists in the operator pod and not the Job manager pod. For remote URLs(as per my understanding), it operator downloads the jar and uploads it to JM.

Yes, that has been my experience as well. It does work in sessions if I provide remote JAR files. I guess I just don’t fully understand why deployment jobs use the deployment image, and session jobs can be configured to run against a deployment, but don’t actually use the deployment’s image defined in the helm chart.