[
https://issues.apache.org/jira/browse/FLINK-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406268#comment-17406268
]
Robert Metzger commented on FLINK-24037:
----------------------------------------
True, that would work as well. However it increases the risk of accidentally
mixing Flink versions, in particular when manually assembling the contents of
the classpath. In a Docker image-based deployment, this wouldn't be much of an
issue, because the version is (usually) determined by the image, but for our
binary distribution as a tarball it could cause issues.
> Allow wildcards in ENABLE_BUILT_IN_PLUGINS
> ------------------------------------------
>
> Key: FLINK-24037
> URL: https://issues.apache.org/jira/browse/FLINK-24037
> Project: Flink
> Issue Type: Improvement
> Components: flink-docker
> Reporter: Robert Metzger
> Priority: Major
>
> As a user of Flink, I would like to be able to specify a certain default
> plugin, (such as the S3 presto FS) without having to specific the Flink
> version again.
> The Flink version is already specified by the Docker container I'm using.
> If one is using generic deployment scripts, I don't want to put the Flink
> version in two locations.
> Suggested solutions:
> a) Allow wildcards in ENABLE_BUILT_IN_PLUGINS
> b) remove the version string from the jars in the distribution
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
