[GEARPUMP-278] Default value skipped for START_CLOCK on ClockService

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.2
• Fix Version/s: 0.8.3
• Assignee: Manu Zhang
• Reporter: Manu Zhang
• Created: 21/Feb/17 01:04
• Updated: 21/Feb/17 02:36
• Resolved: 21/Feb/17 02:36

Description

The cause is when we get START_CLOCK from AppDataStore, it is converted to TimeStamp or Long. If we haven't stored a previous value, then null is expected. That's why we do Option(clock).getOrElse(0L). In fact, 0 is returned when null is converted to Long, which makes the default value useless.

Issue Links

• links to: GitHub Pull Request #154