Hi,   Similar exception can be seen if we do not add credentials block with in the workflow something like below. Do check you have correct credentials if its a kerborized cluster.   <credentials> <credential name="hcatauth_creds" type="hcat"> <property> <name>hcat.metastore.uri</name> <value>thrift://<metastore-fqdn>:9083</value> </property> <property> <name>hcat.metastore.principal</name> <value>hive/_HOST@<REALM></value> </property> </credential>   Regards, Chethan YM ... View more

Hi,   As i seen till now there is no such way to rerun the job automatically when it is failed, I think you have to rerun it manually as you do always.   If you want this type of behaviour you may need to create custom scripts as per your requirements.   Regards, Chethan YM ... View more

Hi @mala_etl ,   It looks like a below known issue: https://issues.cloudera.org/browse/HUE-8717   Do work with Cloudera support to get a patch.   Regards, Chethan YM ... View more

Hi,   To look into the issue we need a complete error stack-trace can you please attach it? Also is this happens every-time after impala restart?   Regards, Chethan YM ... View more

Hi,  Please try to rerun the sqoop import outside of oozie and confirm whether its working or not. If it is working then we need to check it from oozie side. We need a complete stacktrcae of the error.   Regards, Chethan YM ... View more

Hi, You can restrict the amount of memory Impala reserves during query execution by specifying the -mem_limit option. If you set mem_limit=2gb, The query will not use more than 2gb even if it needs.   If you cannot set the memory at the time of execution every-time i think you can create a new resource pool under impala admission control. While creating resource pool you can mention Min and Maximum Query Memory Limit and do not use this resource pool for production queries.    set request_pool="pool-name" run the test queries.   Regards, Chethan YM   ... View more

Hi @HareshAmin ,   As per the below documentation it looks like Hive UDF's are not supported in Impala. Please refer the documentation: https://docs.cloudera.com/documentation/enterprise/5-8-x/topics/impala_udf.html   Regards, Chethan YM ... View more

Hi,   The Reducer process the output of the mapper. After processing the data, it produces a new set of output. At last HDFS stores this output data. Reducer takes a set of an intermediate key value pair produced by the mapper as the input and runs a Reducer function on each of them. The mappers and reducers depends on the data that is processing.   You can manually set the number of reducers with below property but i think it is not recommended. set mapred.reduce.tasks=xx;   Regards, Chethan YM ... View more