[
https://issues.apache.org/jira/browse/MESOS-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431476#comment-15431476
]
Anand Mazumdar commented on MESOS-5788:
---------------------------------------
{noformat}
commit 04b9498bc5b5e080095786f4275c202625b3142b
Author: Anand Mazumdar <[email protected]>
Date: Mon Aug 22 11:14:51 2016 -0700
Renamed `JNIMesos` to `V1Mesos` for scheduler shim.
This change renames `JNIMesos`, v1 implementation for the scheduler
shim to `V1Mesos`. `JNIMesos` was non-intuitive for users considering
the implementation was already in the native code for `V0Mesos` too.
Also, it was a bit confusing that `JNIMesos` referred to using the v1
API under the hood.
Review: https://reviews.apache.org/r/51129/
{noformat}
> 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
> Fix For: 1.1.0
>
>
> 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)
