The idea here was to create, on demand, recovery/committed window. But
there is always one(except before the first) recovery window for the DAG.
Instead of using/modifying the Checkpoint tuple, I am planning to reuse
the existing recovery window state, which simplifies the implementation.
hmm! actually it may be a good debugging tool too. Keep the named
checkpoints around. The feature is to keep checkpoints around, which can be
done by giving a feature to not delete checkpoints, but then naming them
makes it more operational. Send a command from cli->get checkpoint -> know
it is
Sandesh, Agreed.
There should be external APIs to acces the feature, if we want to integrate
it to 3rd party tools.
Thanks,
A
_
Sent with difficulty, I mean handheld ;)
On 4 Aug 2016 8:47 pm, "Sandesh Hegde" wrote:
> @Chinmay
> We
@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
+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
+1
Ram
On Thu, Aug 4, 2016 at 12:10 AM, Sandesh Hegde
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
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
wrote:
> This will be awesome feature. I can see the usecases for production
> scenario
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 wrote:
> Hello Team,
>
> This thread is to discuss the Named