You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/07/12 22:45:20 UTC

[jira] [Commented] (MESOS-5788) Consider adding a Java Scheduler Shim/Adapter for the new/old API.

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

Anand Mazumdar commented on MESOS-5788:
---------------------------------------

The look of new interfaces/classes with the Shim: https://gist.github.com/hatred/ba2c3168f1ef597af2719d13ae44f1fa

> Consider adding a Java Scheduler Shim/Adapter for the new/old API.
> ------------------------------------------------------------------
>
>                 Key: MESOS-5788
>                 URL: https://issues.apache.org/jira/browse/MESOS-5788
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Anand Mazumdar
>            Assignee: Anand Mazumdar
>              Labels: mesosphere
>
> Currently, for existing JAVA based frameworks, moving to try out the new API can be cumbersome. This change intends to introduce a shim/adapter interface that makes this easier by allowing to toggle between the old/new API (driver/new scheduler library) implementation via an environment variable. This would allow framework developers to transition their older frameworks to the new API rather seamlessly.
> This would look similar to the work done for the executor shim for C++ (command/docker executor). 



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