[
https://issues.apache.org/jira/browse/OOZIE-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068459#comment-16068459
]
Peter Cseh commented on OOZIE-2876:
-----------------------------------
I think these are great improvements to Oozie [~clayb]!
However, we're in the middle of finishing up Oozie-on-yarn which is a huge
change (OOZIE-2889) and hitting several issues along the way. Please be patient
while we're make sure the current actions are working properly before we start
adding new ones. We'll get back to these awesome actions soon.
Thanks for the contribution!
> 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.4.14#64029)
