[
https://issues.apache.org/jira/browse/FLINK-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900844#comment-16900844
]
Aljoscha Krettek commented on FLINK-13566:
------------------------------------------
Actually, since quite a while I'm thinking about how we can make *everything*
configurable either using a configuration file, command-line parameters or Java
API. It's a more widespread problem in Flink that some things are only
configurable using one of these. The rough idea in my head is that everything
that is configurable should use some declarative approach, and then
configurable components get their configuration from a configuration object.
The configuration gets into that object from any source, thus unifying
different configuration methods.
I realise this is quite terse, just wrote it down from the top of my head... 😅
> Support checkpoint configuration through flink-conf.yaml
> --------------------------------------------------------
>
> Key: FLINK-13566
> URL: https://issues.apache.org/jira/browse/FLINK-13566
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Checkpointing, Runtime / Configuration
> Reporter: Gyula Fora
> Priority: Major
>
> Currently basic checkpointing configuration happens through the
> StreamExecutionEnvironment and the CheckpointConfig class.
> There is no way to configure checkpointing behaviour purely from the
> flink-conf.yaml file (or provide a default checkpointing behaviour) as it
> always needs to happen programmatically through the environment.
> The checkpoint config settings are then translated down to the
> CheckpointCoordinatorConfiguration which will control the runtime behaviour.
> As checkpointing related settings are operational features that should not
> affect the application logic I think we need to support configuring these
> params through the flink-conf yaml.
> In order to do this we probably need to rework the CheckpointConfig class so
> that it distinguishes parameters that the user actually set from the defaults
> (to support overriding what was set in the conf).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
