Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2517 | 06-11-2020 02:45 PM | |
4044 | 05-01-2020 12:23 AM | |
2126 | 04-21-2020 03:38 PM | |
2092 | 04-14-2020 12:26 AM | |
1717 | 02-27-2020 05:51 PM |
07-24-2019
03:59 AM
Hi, what about if you try to explicitly specify the list of columns, rather than "*"? Also, I am not sure if you read and write to the same table and partition is a good idea. Can you try to create a new table instead? Cheers Eric
... View more
07-19-2019
04:51 PM
Latest driver can be found here: https://www.cloudera.com/downloads/connectors/impala/jdbc/2-6-12.html Suggest you to try a few different versions to see if it is bug in the earlier versions. Thanks Eric
... View more
07-18-2019
10:40 PM
Thanks That's pretty clear now. Can you confirm the version of Impala JDBC driver you are using? Have you tried the latest version to see if the behaviour is the same? Cheers
... View more
07-18-2019
09:12 PM
Hi, Sorry, but your question is really not clear, as you are not giving context. You should have mentioned that you are using Impala JDBC driver. Secondly, sql1 returned lowercase "nickname", but sql2 returned with uppercase "nickName", which query you used setting LowerCaseResultSetColumnName and which one returned correct result? Please provide more information with context around your question, otherwise it is difficult to understand what you are really after. Cheers Eric
... View more
07-18-2019
06:14 PM
Sorry, but what's the issue here? What's the error?
... View more
07-17-2019
05:25 PM
1 Kudo
That's odd, clearly CM tried to get info from "metastore" database, not "scm" database, based on the error message you shared. If you try to change the details in db.properties file, will you get different error message? Like change to wrong password, a database that does not exist? Just to confirm if we are looking at the right property file. Cheers Eric
... View more
07-17-2019
05:22 PM
Hi iamfromsky, To confirm, are you able to change your LB's setting to check less frequent to see if the number of error/warning will also reduce? However, based on my experience, the error produced by LB's tcp check normally is SASL related, not like "java.net.SocketException: Connection reset". It would be good to modify LB setting to confirm though. Cheers Eric
... View more
07-16-2019
07:54 PM
Hi @Cristian.fuentesd, 50010 is the DataNode port: remote=xxxxxxx.xxx.xx/xxx.xx.x.xxx:50010 Have you checked the DataNode log on host xxxxxxx.xxx.xx? (You probably want to mask your host names). Cheers Eric
... View more
07-16-2019
07:07 PM
Hi @dennisli, I think you messed your database up between CM's database vs HMS's database. CM_VERSION table should be under CM's database, not Hive's. What you showed in the list of tables under metastore is for Hive. You should update your database name for CM under /etc/cloudera-scm-server/db.properties. Cheers Eric
... View more
07-15-2019
03:35 AM
Hi, The purpose of compression is to save space, not speed up query time. Compression actually adds overhead to decompress the data before data can be read, so I would expect the query against compressed data will be slightly slower than uncompressed. So what you see is totally normal to me. Cheers Eric
... View more