Issue running Sqoop from Oozie through HUE Web UI

[Santanu Bose]

Issue when using Sqoop command from Oozie (Hue Web UI)

log4j:ERROR Could not find value for key log4j.appender.CLA

I am using the below command in the Sqoop

sqoop list-tables --connect 'jdbc:sap://XXXXXHANA01D:30015?currentschema=XXXXX' --driver com.sap.db.jdbc.Driver --username XXXXX --password XXXXXXXX

[Romain Rigaux]

Which version are you using?

Does it really fail the jobs or is it a warning?

We are going to do a round of improvement on the Sqoop in Oozie in https://issues.cloudera.org/browse/HUE-3878

--
You received this message because you are subscribed to the Google Groups "Hue-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.

[Santanu Bose]

Hi Romain - 

Please find my response below:

Which version are you using? Hue™ 3.9.0 - The Hadoop UI

Does it really fail the jobs or is it a warning? Failed. Please see the error in stderr:

 Log Length: 504

          log4j:ERROR Could not find value for key log4j.appender.CLA

log4j:ERROR Could not instantiate appender named "CLA".

log4j:WARN No appenders could be found for logger (org.apache.hadoop.yarn.client.RMProxy).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

[Santanu Bose]

Hi Romain - 

Please find my response below:

Which version are you using? Hue™ 3.9.0 - The Hadoop UI

Does it really fail the jobs or is it a warning? Failed. Please see the error in stderr:

 Log Length: 504

          log4j:ERROR Could not find value for key log4j.appender.CLA

log4j:ERROR Could not instantiate appender named "CLA".

log4j:WARN No appenders could be found for logger (org.apache.hadoop.yarn.client.RMProxy).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

XML Generated :

<workflow-app name="Test1Oozie" xmlns="uri:oozie:workflow:0.5">

    <start to="sqoop-11c6"/>

    <kill name="Kill">

        <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message>

    </kill>

    <action name="sqoop-11c6">

        <sqoop xmlns="uri:oozie:sqoop-action:0.2">

            <job-tracker>${jobTracker}</job-tracker>

            <name-node>${nameNode}</name-node>

            <command>import --connect &#39;jdbc:sap://XXXXXHANAXXD:30015?currentschema=OTHER&#39; --driver com.sap.db.jdbc.Driver --username XXXXX--password XXXXXXXXX --table REPORT --m 1  --target-dir /raw_data/XXXXXX/Report/ --as-textfile --fields-terminated-by &#39;|&#39; --lines-terminated-by &#39;\n&#39; --check-column CREATEDDATE --incremental append --last-value &#39;2016-08-25 11:04:16.000&#39;</command>

        </sqoop>

        <ok to="End"/>

        <error to="Kill"/>

    </action>

    <end name="End"/>

</workflow-app>

[Romain Rigaux]

I could make it work. Do you ship the hive-site.xml in the lib directory of the workspace? (or point to it in the oozie.libpath?)

Usually any JDBC error will be bubble-up properly, but not sure about the Hive ones.

I also recommend to just do a very basic dump to an HDFS file first (e.g. I did something like 'import --connect jdbc:mysql://localhost/hue --table desktop_document2 --username root --password root --target-dir /user/romain')

[hariom]

Please try this, Got same issue and it's working for me:

step 1 ) add "hive_site.xml" as Files, because it needs table metadata  details

step 2) select "hcat" via Setting-> crdentials->hcat