This should be much easier now that we're using a relational database - we can add a CHECK constraint.
On Fri, Jun 26, 2015 at 11:21 AM, Joe Smith (JIRA) <[email protected]> wrote: > Joe Smith created AURORA-1375: > --------------------------------- > > Summary: When setting quota, the scheduler should prevent > setting below current usage > Key: AURORA-1375 > URL: https://issues.apache.org/jira/browse/AURORA-1375 > Project: Aurora > Issue Type: Story > Components: Scheduler > Reporter: Joe Smith > > > Initially I thought this check should live in the admin client, but after > discussing with [~zmanji], we believe the scheduler would be the right > place to enforce this. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Kevin Sweeney @kts
