Hi, Can you try with below command: select * from bucketing_table tablesample(bucket n out of y on clustered_criteria_column);   n => nth bucket y => total no. of buckets ... View more

@nnandula did you resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.        ... View more

@naush_madaka07 Has your issue been resolved? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.    ... View more

Hello @khanarshadazmat ,   We do not have a direct method to get the CM Server and Agent version like we have in java -version.   However, you can follow some of the below workarounds to get the required result: 1_). using below command # hdfs version # hadoop version 2_). version info available at "/opt/cloudera/parcels/<CDH>/lib/hadoop/cloudera/cdh_version.properties"   Let me know if this helps!   Cheers! 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. ... View more

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

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,   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