Nice feature. +1 for it. One question, instead of creating a new tuple type, can this be done by modifying current checkpoint tuple?
On Thu, Aug 4, 2016 at 2:02 PM, Yogi Devendra <yogideven...@apache.org> wrote: > This will be awesome feature. I can see the usecases for production > scenario as well as developement/troubleshooting environments. > > Excellent value add. > > > > ~ Yogi > > On 4 August 2016 at 12:40, 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 > > >
