You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Hunter L (JIRA)" <ji...@apache.org> on 2018/07/24 21:07:00 UTC

[jira] [Created] (HELIX-744) [TASK] Allow undefined workflow/job types to be assigned as DEFAULT type

Hunter L created HELIX-744:
------------------------------

             Summary: [TASK] Allow undefined workflow/job types to be assigned as DEFAULT type
                 Key: HELIX-744
                 URL: https://issues.apache.org/jira/browse/HELIX-744
             Project: Apache Helix
          Issue Type: Improvement
            Reporter: Hunter L


Previously, we ignored undefined types, that is workflow/job types that are not defined in ClusterConfig. This is not backward-compatible because some users of Task Framework are setting types without any quota-related config set in ClusterConfig. The default behavior was changed so that each AssignableInstance will just treat these workflows/jobs as DEFAULT type, which will make quota-based scheduling backward-compatible. Changelist: 1. AssignableInstance treats undefined types as DEFAULT 2. Appropriate log messages and logic change was applied to restoreTaskAssignResult logic 3. A test case was added to TestQuotaBasedScheduling



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)