[
https://issues.apache.org/jira/browse/SLIDER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305610#comment-14305610
]
Sumit Mohanty commented on SLIDER-773:
--------------------------------------
In general, I am looking at the problem of influencing a slider app package by
adding layers that can modify the file layout, add new config files, or even
modify configs in existing files. You can think of calling "INSTALL" or
"CONFIG" on all add-ons after you have called the same commands for the
original package.
The most common example is likely the problem addressed by SLIDER-757 where
additional jars are being added to the class path. There is also a feature
where you can drop additional config files that will be auto-copied to the
config folder but the expectation is that the config files are fully specified
(_I need to refersh my memory as to how_).
SLIDER-773 will be looking at a general purpose approach that help get around
the limitation that an admin cannot go to a specific host, influence lib dir,
conf dir, etc. when apps are hosted on YARN. Once we have a proposal we can see
if it can effectively subsume the need for {{additional_resource_dir}}.
Another aspect that I am exploring is to not require a .zip file but just
specify a structured folder that may have a metainfo.xml and some files. The
basic form of that is providing a directory where all files in the directory
are copied and made available to AM and container instances.
I will share the proposal on this JIRA soon.
> Add co-processor support for app packages
> -----------------------------------------
>
> Key: SLIDER-773
> URL: https://issues.apache.org/jira/browse/SLIDER-773
> Project: Slider
> Issue Type: Bug
> Components: app-package, client
> Affects Versions: Slider 0.60
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: Slider 0.70
>
>
> It is typical for applications to allow plugins/co-processors that are
> essentially a set of additional jar files in the classpath and optionally a
> set of config files or config changes.
> Current, slider app packages can handle additional config changes/entries
> very well. Additional configs files can be added as well but it is not easy
> if the config files include parameters that need to be resolved by the agent.
> This requires app package changes. Dropping additional jar files into the
> class path is not easy and requires app package changes.
> It is not efficient to modify the app package to support such plugins. App
> packaging and create command should be modified such that the user can
> dynamically specify additional jars, config files, configs etc.
> Specific scenarios are modifying HBase to add support for Phoenix or Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
