[
https://issues.apache.org/jira/browse/FLINK-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704369#comment-16704369
]
Tony Xintong Song commented on FLINK-11034:
-------------------------------------------
I agree with you that we should allow users to config multiple jobs in the same
session differently. However, there are also config options that should remain
consistent during the lifecycle of the whole session. I think the first step
towards this job-specific config issue is probably separate config options into
two categories: job-level configs which should be configured for each job
independently, and session-level configs which should remain consistent. And
probably we should have two config files for the two categories. Otherwise, it
could be troublesome for the user to figure out which config options can be
"rewritten" when submitting a new job to a exist session and which can not.
> Provide "rewriting config” to file system factory
> --------------------------------------------------
>
> Key: FLINK-11034
> URL: https://issues.apache.org/jira/browse/FLINK-11034
> Project: Flink
> Issue Type: Improvement
> Reporter: Wei-Che Wei
> Priority: Major
>
> 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
(v7.6.3#76005)
