@Harsh J   Thank you, unfortunately I have access only to edge node (I can't ssh to masters and workers). I have access to web interfaces though (CM, HUE, Yarn, etc) thus if there is anything I can check from there let me know. ... View more

Thank you, exactly what I was thinking. With all queries aggregated in one script I gain speed (no overhead on Yarn containers) but in case of error I loose granularity for debug. ... View more

Thank you very much for the detailed answer @mzkdm.   This is indeed a very interesting point. Do you think could make sense to have daily-based partitions, since my main ingestion workflow run once a day? And how can I force Hive or Impala users to use the last point-in-time data?   Thanks for the help! ... View more

The second error is normal. You are using the HiveServer1 driver to connect to HiveServer2, that's why it is failing. According to your beeline command, you have HS2.   You need the following URL jdbc:hive2://localhost:10000;AuthMech=0;transportMode=binary with Class.forName("com.cloudera.hive.jdbc4.HS2Driver");   UID is not required, but you can provide it. Since you don't have LDAP configured, you definitelly don't have to set password. ... View more

Thank you for the answer   The JAVA_HOME is not set, and I've installed the jdk version from the CDH repository. Then I guess the Cloudera Manager also installed the jdk 6 during the isntallation/configuration phase.   So you recommend to uninstall jdk 6 and 7 and install the latest supported jdk on each host? ... View more

Hi bgooley, yhank you for the answer! I've set the Sqoop 1 Client Gateway and deployed the configuration. The Teradata Connector parcel was already activated during the cluster configuration phase.   What puzzles me is that in the Cloudera documentation, for the manual installation, says that the following property must be added to the sqoop-site.xml file in order to use the Teradata connector with Oozie:     <configuration> <property> <name>sqoop.connection.factories</name> <value>com.cloudera.connector.teradata.TeradataManagerFactory</value> </property> <configuration>   I've followed the teradata connector installation path trough Cloaudera Manager, thus I was expecting that the property had been injected automatically by the CM, but it seems missing in the sqoop-site.xml files:     /run/cloudera-scm-agent/process/ccdeploy_sqoop-conf_etcsqoopconf.cloudera.sqoop_client_1328941158299821742/sqoop-conf/sqoop-site.xml <?xml version="1.0" encoding="UTF-8"?> <!--Autogenerated by Cloudera Manager--> <configuration> <property> <name>sqoop.connection.factories</name> <value></value> </property> <property> <name>sqoop.tool.plugins</name> <value></value> </property> </configuration>   /etc/sqoop/conf.cloudera.sqoop_client/sqoop-site.xml <?xml version="1.0" encoding="UTF-8"?> <!--Autogenerated by Cloudera Manager--> <configuration> <property> <name>sqoop.connection.factories</name> <value></value> </property> <property> <name>sqoop.tool.plugins</name> <value></value> </property> </configuration> In this case should I inject it manually from the configuration in Cloudera Manager web console as explained from @saranvisa?   Thanks for the help   ... View more