[
https://issues.apache.org/jira/browse/HELIX-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579731#comment-14579731
]
ASF GitHub Bot commented on HELIX-600:
--------------------------------------
GitHub user lei-xia opened a pull request:
https://github.com/apache/helix/pull/29
[HELIX-600] Task scheduler fails to schedule a recurring workflow if the
startTime is set to a future timestamp.
Ticket: https://issues.apache.org/jira/browse/HELIX-600
mvn test passed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lei-xia/helix helix-0.6.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/helix/pull/29.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #29
----
commit a84c9b1f55cb5c01f2c39fb437c6d4effcee3874
Author: Lei Xia <[email protected]>
Date: 2015-06-09T21:40:32Z
[HELIX-600] Task scheduler fails to schedule a recurring workflow if the
startTime is set to a future timestamp.
----
> Task scheduler fails to schedule a recurring workflow if the startTime is set
> to a future timestamp
> ---------------------------------------------------------------------------------------------------
>
> Key: HELIX-600
> URL: https://issues.apache.org/jira/browse/HELIX-600
> Project: Apache Helix
> Issue Type: Bug
> Affects Versions: 0.6.3, 0.6.4
> Reporter: Karthiek
> Assignee: Lei Xia
>
> If we define a recurrent job queue with start-time value in the future (say
> current time + 5 minutes), Helix does not schedule the queue event after
> start-time timestamp elapses. Helix should schedule jobs once the recurrence
> timestamp is hit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
