[jira] [Comment Edited] (OOZIE-2876) Provide deployment primitives

["Clay B. (JIRA)" <ji...@apache.org>]

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

Clay B. edited comment on OOZIE-2876 at 5/3/17 6:56 AM:
--------------------------------------------------------

It seems downloading from a generic HTTP server is a pretty easy activity for a Java or Shell action; have folks seen this onerous enough for new-users that an action could provide value?


was (Author: clayb):
It seems downloading from a generic HTTP server is a pretty easy action for a Java or Shell action; have folks seen this onerous enough for new-users that an action could provide value?

> Provide deployment primitives
> -----------------------------
>
>                 Key: OOZIE-2876
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2876
>             Project: Oozie
>          Issue Type: Wish
>          Components: action
>            Reporter: Clay B.
>            Priority: Minor
>
> Today one can schedule workflows which run on a cluster using many pre-existing artifacts. However, today there are no helpful primitives for deploying those artifacts to the cluster.
> For example, one may use a Spark JAR (hosted in a Maven repository) stored on a cluster's HDFS to talk with data stored in a Hive table (the schema of which is likely tracked in a source code management system somewhere) and use JDBC to talk to an arbitrary database off the cluster. (As to which database being configured based on the cluster being Dev, Beta or PROD all mapped in a simple configuration file.) Further, the data may be verified by a simple Pig script (also stored in a source code management repository).
> As a user, I'd like some way to get my binaries and ASCII configuration on a cluster without significant ad hoc shell actions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)