Page History

...

The goal is to introduce an anchored wall-clock punctuation that will have functionally similarities with that of running a cron job. In short, the user should be allowed to specify the start time for the schedule, instead of relying on the non-deterministic time for when the schedule was registered.

The proposed API change is to extend the `schedule()` method in the `ProcessingContext` interface with a parameter to represent the start time in epoch milliseconds for the schedule's anchored time, without enforcing any changes upon the existing users:

...

The `startTime`, together with the `interval` and the wall clock, will determine the next trigger time for the callback. Hence, the anchored punctuation is only supporting It is planned that only wall clock (i.e. stream time) is supported in this first iteration.

The method for calculating the next, anchored trigger time, could look something like:

...