Looking at the error, it looks like RPC call are timing out and there can be multiple reasons for the same, to get the RCA on this we would require your impala profile and the coordinator logs covering the issue time. ... View more

1. We don't have any official document to connect directly to AWS Glue.   2. We have a document to connect to S3 and move data between S3 and Data lake cluster.   3. you can use BDR and Distcp to achieve the same , the below documents shows the same.   https://blog.cloudera.com/using-amazon-s3-with-cloudera-bdr/ https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/admin_s3_docs_ref.html https://docs.cloudera.com/runtime/7.2.9/scaling-namespaces/topics/hdfs-distcp-with-amazon-s3.html     ... View more

Hello Balaji    1. Could you confirm if you are using the same certificates for both the JDBC and ODBC connection strings?   2. The error looks like more of cert DNS issue un.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid   hat application if it can trust it. The way trust is handled in the Java world is that you have a keystore (typically $JAVA_HOME/lib/security/cacerts), also known as the truststore. This contains a list of all known Certificate Authority (CA) certificates, and Java will only trust certificates that are signed by one of those CAs or public certificates that exist within that keystore. For example, if we look at the certificate for Atlassian, we can see that the *.atlassian.com certificate has been signed by the intermediate certificates, DigiCert High Assurance EV Root CA and DigiCert High Assurance CA-3. These intermediate certificates have been signed by the root  Entrust.net Secure Server CA :     These three certificates combined are referred to as the certificate chain, and, as they are all within the Java keystore (cacerts), Java will trust any certificates signed by them (in this c   This problem is therefore caused by a certificate that is self-signed (a CA did not sign it) or a certificate chain that does not exist within the Java truststore. Java does not trust the certificate and fails to connect to the application. Resolution Make sure you have imported the public certificate of the target instance into the truststore..   Make sure any certificates have been imported into the correct truststore; you may have multiple JRE/JDKs. See Installing Java for this. Check to see that the correct truststore is in use. If -Djavax.net.ssl.trustStore has been configured, it will override the location of the default truststore, which will need to be checked. If this error results while integrating with an LDAP server over LDAPS and there is more than one LDAP server, .  Optionally, import the SSL certificates from the other LDAP servers into the Confluence truststore. Check if your Anti Virus tool has "SSL Scanning" blocking SSL/TLS. If it does, disable this feature or set exceptions for the target addresses (check the product documentation to see if this is possible.) If connecting to a mail server, such as Exchange, ensure authentication allows plain text. Verify that the target server is configured to serve SSL correctly. This can be done with the SSL Server Test tool. If all else fails, your truststore might be out of date. Upgrade Java to the latest version supported by your application.   ... View more

Hello Torow   Looking at the exception [1] it looks like an sentry hive issue , to confirm the same can you please run the query in beeline with same user "hui.min.ang" and same query and share the error you observe,   Could you please confirm what do you mean by "when i open the new table " do you mean creating a new table ?    [1] exceptions_renderable ERROR Potential detail: AuthorizationException: User 'hui.min.ang' does not have privileges to access: default.ipay   Regards Manpreet Singh ... View more

Hello Abhinav   The error message seems generic and there could be multiple reason for this error example service was bad , HMS not able to connect to backend db .   1. Please enabled debug level logging if using hive CLI , this will show us the error which is cuaing this failure:   Below are the steps to enable debug logging for session level   root@hostname ~]# export HADOOP_ROOT_LOGGER=DEBUG,console [root@hostname ~]# hive --hiveconf hive.root.logger=DEBUG,console  -e "create table test(i int)"   2.. Was the hive service up and running when you observed this issue ?   To start HiveServer1: $ sudo service hiveserver start To start the Hive console: $ hive hive> To confirm that Hive is working, issue the show tables; command to list the Hive tables; be sure to use a semi-colon after the command: hive> show tables; OK Time taken: 10.345 seconds 3.. Did you try using Beeline as well ?  if not could you please try connecting via beeline and let us know if that works   Because of concurrency and security issues, HiveServer1 is deprecated in CDH 5 and will be removed in a future release. Cloudera recommends you migrate to Beeline and HiveServer2 as soon as possible. The Hive Console is not needed if you are using Beeline with HiveServer2.   https://blog.cloudera.com/blog/2014/02/migrating-from-hive-cli-to-beeline-a-primer/   Thanks Manpreet Singh           ... View more