Hello,

when using our docker image users can enable certain plugins via an environment variable, listing all plugins they'd like to enable. This is a list of plugin jar names, which contain the full Flink version, like 1.16.1.

This implies that users always need to be aware of the patch version that they are using (because the plugin name has to match exactly); which then means that using the docker tags without a patch version becomes rather tricky, because the actual patch version encoded into the plugin directory may suddenly change.

In https://github.com/apache/flink-docker/pull/158 a proposal was made to add symlinks without the patch version for all plugin directories.

This would work, but I'm not sure if it's the right way to go about this.
Alternatively we could

 * allow globbing patterns to select plugins (e.g., flink-s3-fs*)
     o this adds some complexity to ensure only 1 jar matches the pattern
 * stop encoding the Flink version altogether into the various jars in
   the distribution

On the other hand, we could also stop publishing docker tags without a patch version altogether, because it is a potential trap for users if they are unaware that different processes in a cluster must all run on the same version and you can't just do an in-place upgrade for running jobs.


I can't really decide, and am looking for input from others.


Cheers,
Chesnay

Reply via email to