Member since
08-13-2014
47
Posts
4
Kudos Received
6
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4842 | 03-02-2020 08:35 AM | |
1758 | 09-13-2018 09:10 AM | |
2792 | 07-24-2018 06:09 AM | |
2306 | 04-18-2018 08:17 AM | |
2086 | 01-07-2015 12:01 AM |
03-02-2020
02:25 PM
Hi Luis, If you run SHOW TABLES in the Impala ODBC session do you see the list of tables? Are only the external tables missing? Can you try running SHOW CURRENT ROLES to see if the lost of Sentry roles matches what you expect. I would also recommend checking the Impala logs, these will shed some more light on whether the table is not visible or if you are being denied access. Kind regards, Jim
... View more
03-02-2020
08:35 AM
Hi Luis, There are a couple of suggestions I can make to help narrow down what the cause may be. Are you able to run queries against these tables in Hue using both Impala and Hive? More than just seeing the tables in the navigation on the left are you actually able to SELECT from them using both engines? Are you using the same user in both Hue and the ODBC connection? I ask because if user is not allowed to access a table by Sentry then that table will not appear when you run SHOW TABLES. Have you run SELECT <db_name> in your ODBC SEL session prior to running SHOW TABLES or running a SQL query? Have you tried a SELECT statement on the table even if the metadata is not showing when you run SHOW TABLES? Try prefixing the database name to the table e.g. db_name.table_name. As always you should also check the logs to see if there are any clues as to why it is not working. Check to ensure that the version of the ODBC driver is compatible with the version of Impala you are using. Kind regards, Jim
... View more
07-18-2019
02:36 AM
Hi, In both of these cases it looks like the certificate validation has failed. This typically happens when the Certificate Authority (CA) certificate is missing, has incorrect permissions set or does not have the correct password set. Check that you have added any CA certificates required to your trust store; in this case you need th CA certificate for GlobalSign. You will find details on how to configure TLS for these services in the Cloudera documentation. https://www.cloudera.com/documentation/enterprise/5-16-x/topics/impala_ssl.html https://www.cloudera.com/documentation/enterprise/5/latest/topics/cm_sg_ssl_hue.html Regards, Jim
... View more
09-27-2018
01:37 AM
Edit the file /etc/hosts. It maps the hostname to the IP address. In most cases the quickstart VM gets this right, if you experience an issue restarting usually fixes it. Regards, Jim
... View more
09-18-2018
05:22 AM
It looks like a problem with your SSL/TLS configuration. Check that the trust store contains the correct certificates. When you upgraded the JDK did did you remember to add your certificates to the cacerts truststore? Regards, Jim
... View more
09-13-2018
09:10 AM
No, restarting Cloudera Manager server and agents to pick up the new certificates should not affect any of the Hadoop cluster services. Regards, Jim
... View more
07-24-2018
06:09 AM
Hi, You're probably seeing this because the KDC host configured in Cloudera Manager is different on the two clusters. To check this log into Cloudera Manager and go to Administration -> Settings and then search for KDC Server Host. Regards, Jim
... View more
06-21-2018
01:20 AM
1 Kudo
Do you have the address quickstart.cloudera in /etc/hosts? If this is set incorrectly then trying to access the cluster using the hostname will always attempt to use the old address. Update the address in the hosts file and try again, see if that helps. Regards, Jim
... View more
04-19-2018
09:11 AM
Glad to hear it!
... View more
04-18-2018
08:17 AM
Try running "yum clean all" and try running the installer again. Let me know if that helps. Jim
... View more