Member since
10-04-2017
40
Posts
3
Kudos Received
4
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5460 | 07-05-2021 12:53 AM | |
| 2558 | 05-02-2019 11:27 AM | |
| 2493 | 04-22-2019 05:20 AM | |
| 2240 | 03-17-2019 10:09 PM |
07-05-2021
12:53 AM
Hello I am suspecting that either of below are enabled in impala as these only generate audit logs. Enable Audit Collection Enable Impala Audit Event Generation To be able to disable auditing for Impala service, you need to uncheck both of the above options. Once done make sure to restart Impala service. CM would show stale and restart icon as well.
... View more
06-15-2021
11:17 PM
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
05-02-2019
11:27 AM
1 Kudo
Hello JimBarbour I understand that you are using CDH 5.10 which comes with hive version 1.1 . Currently this version of hive does not support CTAS with partitioned by clause, the functunality is address in hive version 4.0.0, 3.2.0. here is the jira for the same https://issues.apache.org/jira/browse/HIVE-20241 Regards Manpreet Singh
... View more
04-22-2019
05:20 AM
Hello Kais From the error attached above I obsereved some issue with the file place under this directory[2][1], could you please confirm if this directory only contains files and not directories inside. Pleas try with new location and place the corresponding file inside it. [1] hdfs://quickstart.cloudera:8020/user/hive/warehouse/categories:25:24', [2] Bad status for request TFetchResultsReq(fetchType=0, operationHandle=TOperationHandle(hasResultSet=True, modifiedRowCount=None, operationType=0, operationId=THandleIdentifier(secret='\xc3\xd7\x97\xd3coB\xa1\x90P\x9e\xab\x82\xa4\xf4A', guid='\x80\xa1\x93\xe2\x10\xefJ\xd9\xa3\xa3\xdb\x1f\x95\x85\x88\xb3')), orientation=4, maxRows=100): TFetchResultsResp(status=TStatus(errorCode=0, errorMessage='java.io.IOException: java.io.IOException: Not a file: hdfs://quickstart.cloudera:8020/user/hive/warehouse/categories', sqlState=None, infoMessages=['*org.apache.hive.service.cli.HiveSQLException:java.io.IOException: java.io.IOException: Not a file: hdfs://quickstart.cloudera:8020/user/hive/warehouse/categories:25:24', 'org.apache.hive.service.cli.operation.SQLOperation:getNextRowSet:SQLOperation.java:463', Thanks Manpreet Singh
... View more
03-17-2019
10:09 PM
1 Kudo
Hello Rahul Our Hive documentation [1] states currently "Hive in CDH does not support transactions (HIVE-5317)", so you can't use the Insert ,Update and Delete statements in Hive. Based on the requirements you may want to consider using Kudu storage through Impala [2] Please let me know if you have any more questions or concerns. [1] https://www.cloudera.com/documentation/enterprise/5-14-x/topics/hive_ingesting_and_querying_data.html#hive_transaction_support [2] https://www.cloudera.com/documentation/enterprise/5-14-x/topics/kudu_impala.html Thanks Manpreet Singh
... View more