[ 
https://issues.apache.org/jira/browse/FLINK-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900098#comment-16900098
 ] 

Gyula Fora commented on FLINK-13566:
------------------------------------

Thanks for the feedback [~uce] . I am planning to start work on this in a few 
days and can also put together a summary document.

We have used some quick workarounds to enable this behaviour at King which has 
provided great value for new developers (so we could pre-configure 
checkpointing for every job by default). Otherwise it's easy to forget 
configuring checkpointing and also this seems to be something everybody has to 
parameterize their job with all the time anyways adding a lot of boilerplate to 
the StreamExecutionEnvironment setup steps.

> 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)

Reply via email to