@cloudd As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

I was also facing same issue like you. Then I had followed these steps  and it worked for me :   set hive.support.concurrency=true; set hive.enforce.bucketing=true; set hive.exec.dynamic.partition.mode=nonstrict; set hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager; set hive.compactor.initiator.on=true; set hive.compactor.worker.threads=2;   Then I changed added hive.in.test property=true in the hive-site.xml file in /usr/lib/hive location.   After that I restarted the Hive from HUE and then ran the update command and it worked for me. ... View more

Hi Ajay, As I mentioned before in the previous post: Hue will hold the query handler open so that it can do paginations, and it will only kill the handler after user navigates away from the impala page. If user stays on the page, the handler will be kept open and the query is considered as in flight. This is intended and part of design. If you do not want it to be open for long time, you need to set the idle_session_timeout at Impala level. Cheers Eric ... View more

How did you solve the issue?   I am getting the same error.   Unable to instantiate UDF implementation class com.esri.hadoop.hive.ST_Point: java.lang.IllegalAccessException: Class org.apache.hadoop.hive.ql.udf.generic.GenericUDFBridge can not access a member of class com.esri.hadoop.hive.ST_Point with modifiers "" ... View more

there is a possibility that your daemon process is hung find it and kill it $> ps -eaf|grep impala impala 4399 1 0 Aug17 ? 00:00:00 python2.7 /usr/lib64/cmf/agent/build/env/bin/cmf-redactor /usr/lib64/cmf/service/impala/impala.sh impalad impalad_flags false clouder+ 8426 5709 0 16:34 pts/0 00:00:00 grep --color=auto impala impala 12322 1 0 Aug17 ? 00:00:00 /opt/cloudera/parcels/CDH-5.10.1-1.cdh5.10.1.p0.10/lib/impala/sbin-retail/impalad --flagfile=/run/cloudera-scm-agent/process/3639-impala-IMPALAD/impala-conf/impalad_flags $>sudo kill -9 12322 $>sudo kill -9 4399 try to restart your daemon   and check the port $> sudo netstat -lntp|grep 22000   ... View more

@vratmuri   Oh then you can use cloudera API   Link for cloudera API reference: https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cm_intro_api.html   Link for specific to service properties (you may need to explore little for impala query). It may help you https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cm_intro_api.html#xd_583c10bfdbd326ba--7f25092b-13fba2465e5--7f20__example_txn_qcw_yr     ... View more

Thank you @saranvisa Thank you @Divyani ... View more

Before your reply I've rebooted the node after that it's run well.   Now I can see some issue(Port running on other Node) again when I'm running the  COMPUTE STATS command on Impala.   COMPUTE STATS: 1.I have a table with old Parquet data. 2.Now I have added parquet data with New data types(INT TO STRING) for the same columns. 3.I have created new table in the same location with new schema (Impala > CREATE EXTERNAL TABLE database.table2 like parquet '/home/output/university/client=england/campaign=second/details=students/part-r-00111-5fce6c4d-784e-457f-9a01-aa6d6ec1187c.snappy.parquet'; Impala > SHOW CREATE TABLE table2; Then Ive created tablw with table2 schema) 4. /home/output/university/client=england/campaign=second/details=students/part-r-00111-5fce6c4d-784e-457f-9a01-aa6d6ec1187c.snappy.parquet' has an incompatible Parquet schema for column 'mobistat.psrvoicecdma.systemid'. Column type: STRING, Parquet schema: optional int32 systemid [i:22 d:1 r:0]     please help me out in this.     ... View more