Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-2876

Provide deployment primitives

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • action
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            clayb Clay B.
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated: