@Chinmay We can enhance the existing checkpoint tuple but that one is more frequently used than this feature, so why burden Checkpoint tuple with an extra field?
@Aniruddha It is better to leave the scheduling to the users, they can use any tool that they are already familiar with. On Thu, Aug 4, 2016 at 7:40 AM Aniruddha Thombare <anirud...@datatorrent.com> wrote: > +1 On the idea, it would be awesome to have. > > Question: Can we further develop this brilliant idea into:- > Scheduled checkpoints ( To save as dynamically named checkpoint)? > This would be on the lines of logrotate / general backup strategies. > > > Thanks, > > A > > _____________________________________ > Sent with difficulty, I mean handheld ;) > On 4 Aug 2016 8:03 pm, "Munagala Ramanath" <r...@datatorrent.com> wrote: > > > +1 > > > > Ram > > > > On Thu, Aug 4, 2016 at 12:10 AM, Sandesh Hegde <sand...@datatorrent.com> > > wrote: > > > > > Hello Team, > > > > > > This thread is to discuss the Named Checkpoint feature for Apex. ( > > > https://issues.apache.org/jira/browse/APEXCORE-498) > > > > > > Named checkpoints allow following workflow, > > > > > > 1. Users can trigger a checkpoint and give it a name > > > 2. Relaunch the application from the named checkpoint. > > > 3. These checkpoints survive the "purge of old checkpoints". > > > > > > Current idea is to add a new control tuple, NamedCheckPointTuple, which > > > contains the user specified name, it traverses the DAG and along the > way > > > necessary actions are taken. > > > > > > Please let me know your thoughts on this. > > > > > > Thanks > > > > > >
