You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrei Sekretenko (Jira)" <ji...@apache.org> on 2020/10/02 13:37:00 UTC

[jira] [Commented] (MESOS-10189) Pass offer constraints through the V0 scheduler driver and its Java bindings.

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

Andrei Sekretenko commented on MESOS-10189:
-------------------------------------------

{noformat}
commit c28fd3a93e0d9d9a868aec2380abd1dd338304ef
Author: Andrei Sekretenko asekretenko@apache.org
Date:   Thu Oct 1 14:06:59 2020 +0200

Re-added the obsolete `updateFramework` signature into libmesos-java.so.

This patch converts the implementation of the obsolete 2-parameter
`SchedulerDriver.updateFramework(frameworkInfo, suppressedRoles)`
from a wrapper around the new signature back into a JNI method
that 930c7e98d17e71192dae1d49b4b2217cc2dbd8b2 attempted to remove.

This is needed to keep compatibility between older versions of
`mesos.jar` and newer versions of `libmesos-java.so`.

Review: https://reviews.apache.org/r/72922
{noformat}

> Pass offer constraints through the V0 scheduler driver and its Java bindings.
> -----------------------------------------------------------------------------
>
>                 Key: MESOS-10189
>                 URL: https://issues.apache.org/jira/browse/MESOS-10189
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Andrei Sekretenko
>            Assignee: Andrei Sekretenko
>            Priority: Critical
>             Fix For: 1.11.0
>
>
> At the very least, in the updateFramework call.
> Passing through constructor is not that critical.
> Without this, the V0 frameworks (including Marathon, which is the primary candidate for adoption of offer constraints) will not be able to set the constraints.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)