Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3335
@WangTaoTheTonic Am I right in assuming that your scenario assumes that
multiple different users submit Flink jobs and these jobs cannot be "prepared"
by a script that sets up a dedicated checkpoint directory with the respective
permissions?
If we see that as a use case we want to support, then I could see this as
an optional feature of the `FsStateBackend`. The configuration for that backend
could take an optional parameter `state.backend.fs.permissions`. If that
parameter is non-null, the state backed applies it onto the root directory.
That way we keep the change local to the `FsStateBackend` (which is implicitly
also used by the RocksDBStateBackend) and optional.
What you all think about that proposal?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
