gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEARPUMP-278) Default value skipped for START_CLOCK on ClockService
Date Tue, 21 Feb 2017 01:04:44 GMT
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)

Mime
View raw message