You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2017/02/21 01:04:44 UTC

[jira] [Created] (GEARPUMP-278) Default value skipped for START_CLOCK on ClockService

Manu Zhang created GEARPUMP-278:
-----------------------------------

             Summary: 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


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)