[
https://issues.apache.org/jira/browse/APEXCORE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688437#comment-15688437
]
Sanjay M Pujare commented on APEXCORE-498:
------------------------------------------
If a user decides to use savepoints (named checkpoints), the platform cannot
guarantee end-to-end exactly once or should not be expected to guarantee, isn't
that right? And especially if the use-case is reprocessing. In such a case, if
some of these guarantees are relaxed, doesn't the feature boil down to just the
ability to name checkpoints and restore from these checkpoints (and related
book-keeping).
> Named Checkpoints - Checkpoint the DAG with a name/tag and start the app from
> that point
> ----------------------------------------------------------------------------------------
>
> Key: APEXCORE-498
> URL: https://issues.apache.org/jira/browse/APEXCORE-498
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Sandesh
> Assignee: Sandesh
> Labels: roadmap
>
> Named Checkpoints
> 1. Ability to tag/name the checkpoints
> 2. On demand - checkpoint the DAG
> 3. Start the app from the named checkpoints
> All checkpoints that happened before the committed window is deleted but the
> named checkpoints won't be deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
