Uploaded image for project: 'Hue (READ ONLY)'
  1. Hue (READ ONLY)
  2. HUE-2737

Ability for oozie Sqoop V1 workflow to use args vs one command option

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Works for Me
    • Affects Version/s: 3.8.0
    • Fix Version/s: None
    • Component/s: con.oozie
    • Labels:

      Description

      Ability to instead of providing the Sqoop Command option as one string which can cause trouble with DB2 connection options due to spaces etc.. Is it an option to have Oozie WorkFlow Editor provide an option to use args as described here in this article:
      http://archive.cloudera.com/cdh5/cdh/5/oozie/DG_SqoopActionExtension.html#Sqoop_Action

      The same Sqoop action using arg elements:

      <workflow-app name="sample-wf" xmlns="uri:oozie:workflow:0.1">
      ...
      <action name="myfirsthivejob">
      <sqoop xmlns="uri:oozie:sqoop-action:0.2">
      <job-traker>foo:8021</job-tracker>
      <name-node>bar:8020</name-node>
      <prepare>
      <delete path="${jobOutput}"/>
      </prepare>
      <configuration>
      <property>
      <name>mapred.compress.map.output</name>
      <value>true</value>
      </property>
      </configuration>
      <arg>import</arg>
      <arg>--connect</arg>
      <arg>jdbc:hsqldb:file:db.hsqldb</arg>
      <arg>--table</arg>
      <arg>TT</arg>
      <arg>--target-dir</arg>
      <arg>hdfs://localhost:8020/user/tucu/foo</arg>
      <arg>-m</arg>
      <arg>1</arg>
      </sqoop>
      <ok to="myotherjob"/>
      <error to="errorcleanup"/>
      </action>
      ...
      </workflow-app>

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gss2002 Greg Senia
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: