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

Posted to dev@myriad.apache.org by "John Yost (JIRA)" <ji...@apache.org> on 2016/05/17 19:58:12 UTC

[jira] [Commented] (MYRIAD-203) Update NodeTask constructor to ensure uniqueness

    [ https://issues.apache.org/jira/browse/MYRIAD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287432#comment-15287432 ] 

John Yost commented on MYRIAD-203:
----------------------------------

This can be accomplished by retaining default equals method (returns false if the two object references are to duplicate instances with same state) as it is now, but it would be safer if the object state of each NodeTask is unique.

> Update NodeTask constructor to ensure uniqueness
> ------------------------------------------------
>
>                 Key: MYRIAD-203
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-203
>             Project: Myriad
>          Issue Type: Bug
>            Reporter: John Yost
>
> The NodeTask constructor does not currently ensure uniqueness in that two NodeTasks could have the same ServiceResourceProfile and Constraint, even though they are separate NodeTask objects.



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