[
https://issues.apache.org/jira/browse/FLINK-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11034:
-----------------------------------
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.
> Provide "rewriting config” to file system factory
> --------------------------------------------------
>
> Key: FLINK-11034
> URL: https://issues.apache.org/jira/browse/FLINK-11034
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem, FileSystems
> Reporter: Wei-Che Wei
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> In the discussion in this mailing thread
> [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/how-to-override-s3-key-config-in-flink-job-td24606.html],
> it showed that it is not able to overwrite config in file system factory
> when submit a flink job.
> That means we will share the same config for multiple jobs in a session
> cluster. Or user can't use different configuration for checkpointing and file
> sink. For example, user might have different s3 buckets for checkpointing and
> file sink, but each of the s3 bucket might have different s3 access key for
> some management concerns.
> We might need to provide a way to overwrite configuration when calling file
> system factory "get" method, and let those user facing components, like
> checkpointing or file sink, will be able to get overwriting config from user
> and create a file system with those changes in the new config.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
