[
https://issues.apache.org/jira/browse/FLINK-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012369#comment-15012369
]
ASF GitHub Bot commented on FLINK-2429:
---------------------------------------
GitHub user StephanEwen opened a pull request:
https://github.com/apache/flink/pull/1382
[FLINK-2429] [streaming] Deprecate the "enableCheckpointing()" method with
no interval argument.
The default checkpoint interval is a bit intransparent. Dropping that
method makes the user think about what interval they want to chose.
We could (and should) later add a way that auto-tunes the checkpoint
interval, based on the time checkpoints take to complete.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StephanEwen/incubator-flink
deprecate_checkpoint_no_arg
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1382.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1382
----
commit cb76e829f44c9f785c9fbce7a0aaead4a6615c32
Author: Stephan Ewen <[email protected]>
Date: 2015-11-17T13:12:45Z
[FLINK-2429] [streaming] Deprecate the "enableCheckpointing()" method with
no interval argument.
----
> Remove the "enableCheckpointing()" without interval variant
> -----------------------------------------------------------
>
> Key: FLINK-2429
> URL: https://issues.apache.org/jira/browse/FLINK-2429
> Project: Flink
> Issue Type: Wish
> Components: Streaming
> Reporter: Stephan Ewen
> Priority: Minor
> Fix For: 1.0.0
>
>
> I think it is not very obvious what the default checkpointing interval is.
> Also, when somebody activates checkpointing, shouldn't they think about what
> they want in terms of frequency and recovery latency tradeoffs?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
