aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "brian wickman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-199) It's not possible to mix limit and attribute constraints
Date Sat, 08 Feb 2014 01:37:19 GMT
brian wickman created AURORA-199:
------------------------------------

             Summary: It's not possible to mix limit and attribute constraints
                 Key: AURORA-199
                 URL: https://issues.apache.org/jira/browse/AURORA-199
             Project: Aurora
          Issue Type: Bug
          Components: Client
            Reporter: brian wickman


A user had a valid need for the following use-case:

{noformat}
constraints = {
  'host': 'hostname1',
  'host': 'limit:2'
}
{noformat}

in order to pin 2 instances of a job to the same host.  Pystachio Map is a multimap but it
gets coerced to a Python dictionary when converting to a set of Thrift Constraint objects,
and the 'multi-' part of the mapping is lost.

We should probably add a new delimiter, e.g. ';' in order to allow for mixes of limit and
attribute constraints, e.g. 'host': 'hostname1;limit:2'




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message