Hi @pauljoshiva ,   Sqoop uses local hive which does automatic connect so you would need to modify the information in beeline-site.xml as referenced in below article:   https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-Usingbeeline-site.xmltoautomaticallyconnecttoHiveServer2   Hence please go to /usr/hdp/<VERSION>/hive/conf then open the beeline-site.xml and modify there.   Regards, Chethan YM ... View more

Hi,   Are you using --password-file option inside your workflow? I have found a bug[1][2] similar to the issue you are facing. If this is the issue can you turn off the uber mode and try the job?   <global> <configuration> <property> <name>oozie.launcher.mapreduce.job.ubertask.enable</name> <value>false</value> </property> </configuration> </global>   Also are you doing any FileSystem.close() call in your actions?  FileSystem objects are automatically cached in Hadoop and thereby if you close the FileSystem object inside from your Java Action Class, which runs in the same JVM as the launcher map task, the singular FileSystem instance itself gets closed. Hence, when the Wrapper/Launcher wishes to exit normally.   Regards, Chethan YM Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   [1]. https://issues.apache.org/jira/browse/SQOOP-2997 [2]. https://jira.cloudera.com/browse/CDH-43107       ... View more

Hi @wasimakram ,   Are you facing any issues/errors while calling the hive script ? can you share your workflow.xml file to have a look? Below is the simple example for it:   <workflow-app xmlns = "uri:oozie:workflow:0.4" name = "simple-Workflow">    <start to = "fork_node" />        <fork name = "fork_node">       <path start = "Create_External_Table"/>       <path start = "Create_orc_Table"/>    </fork>        <action name = "Create_External_Table">       <hive xmlns = "uri:oozie:hive-action:0.4">          <job-tracker>xyz.com:8088</job-tracker>          <name-node>hdfs://rootname</name-node>          <script>hdfs_path_of_script/external.hive</script>       </hive>            <ok to = "end" />       <error to = "kill_job" />    </action>        <kill name = "kill_job">       <message>Job failed</message>    </kill>        <end name = "end" />   </workflow-app>   Regards, Chethan YM ... View more

Hi,   I have found a another community article that has addressed your concern. Please do check below:   That sounds like all is working as designed/implemented since Ranger does not currently (as of HDP 2.4) have a supported plug-in for Spark and knowing that when spark is reading Hive tables that it really isn't going through the "front door" of Hive to actual run queries (it is reading these files from HDFS directly). That said, the underlying HDFS authorization policies (either w/or w/o using Ranger) will be honored if they are in-place.   Article: https://community.cloudera.com/t5/Support-Questions/Does-Spark-job-honor-Ranger-hive-policies/td-p/147760   Do mark it resolved if it really helps you.   Regards, Chethan YM ... View more

Hi,   These are the just health tests of impala daemon processes, Are you facing any query failures due to these tests? I think all these should recover with in a minutes and can be tuned accordingly. Please refer the below cloudera documentation for more details on these health tests. https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ht_impala_daemon.html Regards, Chethan YM ... View more

Hi,   Is this is only the spark job failing with OOM error? what was the initial executor and driver memory that you have tried with? Can you also try to into increase the num-executors and executor-cores and run the job? rerun the job by increasing executors and cores and see if it works.   Regards, Chethan YM ... View more

Hi,   1. Are you able to see the databases outside of hue as a testuser?  2. User and group mapping should be proper and correct to access the databases, please compare the user groups who have access and who doesn't have access.   3. id -Gn <user-id> ( it shows the allocated groups and compare with other users who have access  if any groups are missing add the user to that group and give a try )   4. If testuser user cannot see the databases throgh impala-shell and you have given proper privileges then something might messed up at os level with user group mappings, you can try restarting the SSSD and clear cache of SSSD on all hosts and give a try.   Regards, Chethan YM   ... View more

Hi,   Is this your new oozie setup? or was it running fine earlier? Is oozie service up and running?   Can you provide the output for below commands to verify job status and its logs:( Replace the workflow id ) a. oozie job -oozie http://<oozie-server-host>:11000 -info <workflow-id> b. oozie job -oozie http://<oozie-server-host>:11000 -log <workflow-id>   Regards, Chethan YM   ... View more