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

Posted to commits@helix.apache.org by "Lei Xia (JIRA)" <ji...@apache.org> on 2015/11/21 00:48:11 UTC

[jira] [Created] (HELIX-615) Naming problem of scheduled jobs from recurrent queue.

Lei Xia created HELIX-615:
-----------------------------

             Summary: Naming problem of scheduled jobs from recurrent queue.
                 Key: HELIX-615
                 URL: https://issues.apache.org/jira/browse/HELIX-615
             Project: Apache Helix
          Issue Type: Bug
            Reporter: Lei Xia
            Assignee: Lei Xia


Problem: 
Jobs from a recurrent queue are named with original job + index (for example, if job named backup_job_testdb, the first scheduled job is called backup_job_testdb_0, the second time it gets schedule will be named backup_job_testdb_1, etc.  This will create name conflict if the workflow is deleted and recreated recently.

Proposed Change:
Jobs from a recurring are named with original job + schedule_time (for example, if job named backup_job_testdb, scheduled job will be named backup_job_testdb_20151028T230011Z (Date follows ISO 8601 format).  This will avoid name conflict even if the workflow is deleted and recreated again. 
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)