[
https://issues.apache.org/jira/browse/FLINK-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17557:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Add configuration to disallow ambiguous file schemes
> ----------------------------------------------------
>
> Key: FLINK-17557
> URL: https://issues.apache.org/jira/browse/FLINK-17557
> Project: Flink
> Issue Type: Improvement
> Components: FileSystems
> Reporter: Seth Wiesman
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Flink supports usage of both S3 presto and S3 hadoop within the same session
> via the plugin system. When this happens the scheme 's3://' is and references
> whichever filesystem happened to have been loaded last. Instead, users should
> use the schemes 's3p' and 's3a' respectively which are unique.
> There should be a configuration option that disallows the use of ambiguous
> file schemes to prevent strange behavior in produciton.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
