Read through the documentation of AWS Managed Flink, especially the "Runtime Properties" part, I do not find any mentioning about setting the main class for a given Flink jar.
The example it gives fixates the main class inside the POM.xml.
My case is that I have a multi-purpose Flink App that have multiple entrypoints - represented by multiple main classes - each carries out one specialized kind of job. These jobs, however, are similar in nature so it is reasonable to share a collection of utility classes, and coexist in the same code repository and be shipped together in one single jar file.
Unable to set entryclass on app start means I have to duplicate the shared utility classes and separate jobs into individual jars.
I maybe missed something, so I would like to consult more experienced professionals that can I conclude the, for the current AWS Managed Flink, it is impossible to set the main class on starting an app, but must be hardcoded into the executable jar?