I think any jars in $FLINK_HOME/lib gets picked up in the class path. As for dynamic update, wouldn't you want to run it through your tests/CI before deploying?
FWIW we also use a fat jar. Its large but also since we just build a docker container anyway it doesn't really matter. Tim On Wed, Jul 3, 2019, 5:39 AM Halfon, Roey <roey.hal...@sap.com> wrote: > Hi All, > We have an application which contains few modules (one for the main > application with the "driver" and few other for the operators > implementation, configuration etc.). > At the moment we are building fat jar contains all the modules and all the > 3rd parties dependencies. > > As we continue develop, the jar will grow and grow till it will be heavy. > > Is there any recommendation for using our libraries? Maybe to use them as > dependencies to our application? Does flink have any capability of > dynamically update for 3rd party jars? > > > > How do you build your application? > > Thanks, > Roey. >
