[
https://issues.apache.org/jira/browse/HELIX-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554966#comment-16554966
]
Hudson commented on HELIX-744:
------------------------------
FAILURE: Integrated in Jenkins build helix #1526 (See
[https://builds.apache.org/job/helix/1526/])
[HELIX-744] Allow undefined workflow/job types to be assigned as DEFAULT
(narendly: rev 6759040956907b197b6d65cb8b4759b7e8981883)
* (edit)
helix-core/src/test/java/org/apache/helix/integration/task/TestQuotaBasedScheduling.java
* (edit)
helix-core/src/main/java/org/apache/helix/task/assigner/AssignableInstance.java
* (edit)
helix-core/src/test/java/org/apache/helix/task/assigner/TestAssignableInstance.java
> [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
> Priority: Major
>
> 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)
