Hi, It seems like your host from where you are running Sqoop command is not able to connect on the machine where your mysql is installed.   Kindly run the below command to check the connectivity. ## telnet <hostname> 3306   Note:- Hostname is the host where you have installed mysql database.   In the sqoop command i can see you have provided "localhost" double check it is the one where mysql database is installed.   Below is the command to get the full hostname of the host. ## hostname -f ... View more

Hi, Not sure this info is available. 1. you can check the yarn application logs in hdfs under /tmp/logs you can find this exact path by going to Cloudera manager -> Yarn -> Configuration -> yarn.nodemanager.remote-app-log-dir   2. If you have an application id you can just collect the logs manually with below command:    ##  yarn logs -applicationId <application ID>  > applogs.txt   ... View more

Hello,   When you are facing this issue? For what type of query? How you are created these tables? Is the client (if non beeline or hive) creating the Table have a ACID read/write capability? Can you provide your DDL of this query? ... View more

Hi ,   Can you add this below property in Hive service advance configurations and restart the stale configs and check the issue?   ##  hive.txn.stats.enabled=false   ... View more

Also should check the output of the query from both hive and Impala, If there is any issues with metadata update after REFRESH we need to check the catalog logs at the same time... ... View more

Hi,   I am not sure above issue is resolved or not, As per the issue description after REFRESH you are not able to query the table partition in impala but as per the query details you have given i do not see an issue but it just says stats are missing and your query might have succeeded ( I do not know the query status since you haven't given in the details) If partition is not available the query usually fails with "Analysis Exception". If you have such issue you can upload full query profile and its coordinator logs to check the issue.   ... View more

Hi,   These errors are generic errors that can see in the front end and these errors doesn't shows exact issue.   Regarding the Error #1: Please check "Setting Up the Kerberos Credential Cache File"  for  credential cache for windows in the below documentation. https://www.cloudera.com/documentation/other/connectors/impala-odbc/latest/Cloudera-ODBC-Driver-for-Impala-Install-Guide.pdf   Also upgrade the ODBC connector to the latest version.   Regarding the Error #2: It says "Unexpected response received from server" you need to check the below things to identify the issue: ( Power BI -> ODBC Driver -> LB -> Impala Daemon ) a. Check the ODBC driver logs at the time of issue , If you do not find anything enable trace level logs and check the errors. b. If you have LB configured check the LB logs. c. Try to connect manually for every impala daemon to find out if there is any issue with particular daemon. d. If you faced an issue with connecting any daemon check the logs for more details.   ... View more

Hi    I think you can try out below two options: 1.  Increase idle_session_timeout value in impala 2.  Rewrite the script to open Impala connection just before Impala related commands will be invoked. ... View more