GitHub user ishark opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/250

    APEXCORE-10 #resolve Changes for supporting anti-affinity in operators

    Added list of affinity rules as attribute in DAGContext
    Added validation for affinity, anti-affinity and locality rules in dag 
validate phase
    Added handling of Container and Node affinity rules. Rack affinity is not 
supported at this point
    Also added Changes for supporting Node specific request in Cloudera
    Added Unit tests for affinity rules and dag validation for the same
    Added Json String codec for setting affinity rules through properties.xml
    Added Set Affinity and anti -affinity APIs to dag

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ishark/incubator-apex-core APEXCORE-10

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-apex-core/pull/250.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 #250
    
----
commit d62a21e73b069fc66af0102f8b8884758abfb252
Author: ishark <[email protected]>
Date:   2016-02-29T22:16:51Z

    APEXCORE-10 #resolve Changes for supporting anti-affinity amongst operators
    Added list of affinity rules as attribute in DAGContext
    Added validation for affinity, anti-affinity and locality rules in dag 
validate phase
    Added handling of Container and Node affinity rules. Rack affinity is not 
supported at this point
    Also added Changes for supporting Node specific request in Cloudera
    Added Unit tests for affinity rules and dag validation for the same
    Added Json String codec for setting affinity rules through properties.xml
    Added Set Affinity and anti -affinity APIs to dag

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to