[
https://issues.apache.org/jira/browse/SLIDER-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238681#comment-15238681
]
ASF subversion and git services commented on SLIDER-777:
--------------------------------------------------------
Commit 4b4e24f6c2bcc491b4754085935094c739e33a79 in incubator-slider's branch
refs/heads/feature/SLIDER-906_docker_support from [~gsaha]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=4b4e24f ]
SLIDER-777 Provide slider dependencies as a self contained versioned tarball -
accept system property as a higher priority
> Provide slider dependencies as a self contained versioned tarball
> -----------------------------------------------------------------
>
> Key: SLIDER-777
> URL: https://issues.apache.org/jira/browse/SLIDER-777
> Project: Slider
> Issue Type: New Feature
> Components: build, client
> Affects Versions: Slider 0.70
> Reporter: Sumit Mohanty
> Assignee: Gour Saha
> Priority: Critical
> Fix For: Slider 0.81
>
> Time Spent: 32h
> Remaining Estimate: 10h
>
> Currently, slider client picks up all the dependencies from the lib folder.
> This causes an issue for code that embed Slider client where either they need
> to specify a folder which has the all the required (but no more) jar files or
> their own lib directory which contains jar files of the embedding application
> as well.
> Slider should explore (similar to Tez or MR) the possibility of packaging all
> dependencies into a tarball that can be stored in a version aware fashion in
> HDFS or local FS.
> A Slider client can choose to use a specific version when creating the an
> instance of an application. Now, it is possible for a client of certain
> version to create an app using another version of the tarball. _This requires
> further investigation in terms of how easy to debug the issues if there is no
> compatibility between versions of the client and the tarball._
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
