[REEF-1532] Pass Time object instead of numeric timestamp in Timer methods

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: REEF-Common
• Labels: deprecation
• Assignee: Sergiy Matusevych
• Reporter: Sergiy Matusevych
• Created: 14/Aug/16 04:52
• Updated: 17/Aug/17 07:02

Description

Methods in Timer interface, e.g. Timer.isReady() accept long timestamp, but in all contexts where the Timer implementations are used, we operate with Time objects. That leads to awkward chain calls, e.g.

timer.getDuration(event.getTimeStamp())

instead of shorter and more readable and type safe

timer.getDuration(event)

We propose to deprecate methods that take long timestamp in release 0.16 in favor of parameters of type Time and remove old methods in teh subsequent release.

Issue Links

• blocks: REEF-1868 Release 0.17
• is blocked by: REEF-1444 Release 0.16
• requires: REEF-1527 Graceful shutdown of the RuntimeClock is not so graceful: unconditionally clears the event queue