[
https://issues.apache.org/jira/browse/GEARPUMP-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu Zhang resolved GEARPUMP-278.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.8.3
Issue resolved by pull request 154
[https://github.com/apache/incubator-gearpump/pull/154]
> Default value skipped for START_CLOCK on ClockService
> -----------------------------------------------------
>
> Key: GEARPUMP-278
> URL: https://issues.apache.org/jira/browse/GEARPUMP-278
> Project: Apache Gearpump
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Manu Zhang
> Assignee: Manu Zhang
> Fix For: 0.8.3
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
