What ever is available in your CDH distribution. If you're using parcels, take a look at /opt/cloudera/parcles/CDH/jars. If you're using packages, take a look at /usr/lib/kite. You can upload that jar to any directory in HDFS and make it available to your workflow by including it using the "file" element (https://oozie.apache.org/docs/4.0.0/WorkflowFunctionalSpec.html#a3.2.2.1_Adding_Files_and_Archives_for_the_Job). That would probably be the easiest way to test. ... View more

We're still working on better facilities to look at Sqoop2 logs, but there are currently a few locations you can look (depending on your error). I'm assuming Sqoop2 starts fine, but a job you're running is failing. If that is the case, then your logs should be under /var/log/sqoop2/ and in its associated task/attempt logs. You can view these logs through the Yarn UIs (usually on port 8088. e.g. http://example.com:8088) or through Hue (http://gethue.com/). ... View more

Hey folks, A few notes on getting Sqoop2 to work and give more detail if there is an error: 1. The Derby jar is required for Sqoop2 to work. It does come packaged with Sqoop2, so do not put it into /var/lib/sqoop2. 2. You can use "set option --name verbose --value true" to see more error information. You may be having different errors for all we know. ... View more

From the CLI, Hadoop normally shows: "ls: Permission denied: user=admin..." if you don't have permission. What is your --target-dir set to? ... View more

It seems like the job didn't run. Are you sure it finished? There should be task logs associated with your job. Could you check them for errors? Also, make sure --verbose is in your command for the best possible debug information. ... View more

Sqoop2 is going throgh a lot of changes and isn't supported in Hue in CDH 5.3.0. It should be in CDH 5.3.2 AFAIK.   The Sqoop1 command you are running have two different problems: The postgresql jdbc driver jar isn't available on one of your nodes. This can be fixed by downloading it and putting it in /var/lib/sqoop. The problem seems to be some kind of SQL error. Could you add --verbose to your sqoop command? sqoop import --verbose ... ... View more

Check your connection URL as well. sqoop import --connect jdbc:sqlserver://server;database=db --table table ... View more

Glad it worked. Does that mean your job is running now? ... View more