[
https://issues.apache.org/jira/browse/FLINK-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406410#comment-17406410
]
Chesnay Schepler commented on FLINK-24037:
------------------------------------------
> This could backfire if people have the hadoop s3 plugin, and now get a new
> Flink docker image with the hadoop and presto s3 filesystem implementations,
> because then s3 will default to the presto implementation.
That's a good point; S3 would be a problem.
Could we define a FLINK_VERSION environment variable in our Dockerfiles that
you could make use of? I could see this being useful for other things as well.
The thing is, I don't particularly like how ENABLE_BUILT_IN_PLUGINS currently
works, and would prefer to not extend it further.
> 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)
