aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1485) TaskConfig default container value breaks client library generation for GO
Date Thu, 17 Sep 2015 16:51:04 GMT

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

Hudson commented on AURORA-1485:
--------------------------------

SUCCESS: Integrated in Aurora #1194 (See [https://builds.apache.org/job/Aurora/1194/])
AURORA-1485: TaskConfig default container value breaks client library generation for GO (jfarrell:
rev d98bfc8f4f7bb583b81f052903bfb39b632f0dbf)
* api/src/main/thrift/org/apache/aurora/gen/api.thrift


> TaskConfig default container value breaks client library generation for GO
> --------------------------------------------------------------------------
>
>                 Key: AURORA-1485
>                 URL: https://issues.apache.org/jira/browse/AURORA-1485
>             Project: Aurora
>          Issue Type: Story
>          Components: Client
>            Reporter: Jake Farrell
>            Assignee: Jake Farrell
>             Fix For: 0.10.0
>
>
> When generating the client api library for go the default containerizer used as a hack
for AURORA-1185 breaks and causes the client lib to not be generated correctly. The default
value for the optional field `container = { "mesos": {} }` is not necessary as it is defaulted
in java code on the api side. 
> Tracking this down it looks like the default value was a last minute addition based on
some review comments and is not necessary or used anywhere. Removing the default value does
not impact anything. 



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

Mime
View raw message