You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2013/11/11 09:30:19 UTC
[jira] [Commented] (FALCON-185) Timestamp handled as int
[ https://issues.apache.org/jira/browse/FALCON-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818771#comment-13818771 ]
Srikanth Sundarrajan commented on FALCON-185:
---------------------------------------------
+1. Thanks
> Timestamp handled as int
> ------------------------
>
> Key: FALCON-185
> URL: https://issues.apache.org/jira/browse/FALCON-185
> Project: Falcon
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Fix For: 0.4
>
> Attachments: FALCON-185.patch
>
>
> In LateRerunHandler,
> public static Date addTime(Date date, int milliSecondsToAdd) {
> return new Date(date.getTime() + milliSecondsToAdd);
> }
> endTime = addTime(endTime, (int) feedCutOffPeriod);
> Changing msecs as int makes the timestamp -ve if the value is big. Thanks [~samarthg] for pointing this issue
--
This message was sent by Atlassian JIRA
(v6.1#6144)