[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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.3.4#803005)
