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

Posted to issues@aurora.apache.org by "Brian Brazil (JIRA)" <ji...@apache.org> on 2015/04/17 20:03:58 UTC

[jira] [Commented] (AURORA-1268) Executor is not backwards compatible with regards to schema additions

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

Brian Brazil commented on AURORA-1268:
--------------------------------------

Upstream has accepted my patch (https://github.com/wickman/pystachio/pull/15), so the pystachio dependency needs to be updated and someone verify that we're now backwards compatible.

> Executor is not backwards compatible with regards to schema additions
> ---------------------------------------------------------------------
>
>                 Key: AURORA-1268
>                 URL: https://issues.apache.org/jira/browse/AURORA-1268
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Executor
>            Reporter: Joshua Cohen
>            Priority: Critical
>
> In AURORA-1266 we had to roll back a change due to new fields in the config schema. When a client was built from this change sent a Job to the scheduler, an Executor that was not aware of the new fields would choke on the unexpected properties. This is due to an underlying bug in pystachio: https://github.com/wickman/pystachio/issues/16.
> Once this bug is addressed, we should update our pystachio dependency ASAP.



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