Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4319 | 06-11-2020 02:45 PM | |
5930 | 05-01-2020 12:23 AM | |
3752 | 04-21-2020 03:38 PM | |
4035 | 04-14-2020 12:26 AM | |
2984 | 02-27-2020 05:51 PM |
01-16-2019
08:55 AM
1 Kudo
Kudu runs as a separate service that Impala talks to (like HDFS runs as a separate service from Impala) so you have to have Kudu running somewhere for it to work. However you don't have to run Kudu on the same servers that you run Impala on -- remote reads are supported over the network.
... View more
01-15-2019
11:33 PM
thank you for your answer. I understood that the Catalog Server requires a CPU as well as Impalad.
... View more
01-15-2019
11:01 PM
The whole stacktrace is pointing to Spotfire classes, looks like Spotfire issue. What's the exact error you get from Impala side? What query was run? Do you have PROFILE of the failed query to share?
... View more
01-15-2019
10:27 PM
LATERAL VIEW is not available in Impala yet, see below link: https://www.cloudera.com/documentation/enterprise/latest/topics/impala_langref_unsupported.html#langref_hiveql_unsupported Currently only Hive supports it.
... View more
01-08-2019
02:25 PM
2 Kudos
Hi Rockem, The issue you are facing is due to hdfs permission. By default with "Store in default location" checked during hive table creation through Hue, we are trying to move the data to '/user/hive/warehouse' directory. The user you logged in don't have permission to move data to '/user/hive/warehouse', so table is created successful but no data. You can either grant the user with write permission to '/user/hive/warehouse' or uncheck the "Store in default location" checkbox so it creates external table without moving the file to '/user/hive/warehouse'. Then you will be abl e to see the data. Hope this helps! Weixia
... View more
12-30-2018
03:17 PM
Hi, The directory that contains the list of workflows won't have the name you defined, they are system generated names. You will need to go to the Oozie Workflow List in Hue, search by the name and check the workflow's location, then go to that directory in HDFS. Like below: Then check the workspace name:
... View more
12-29-2018
12:13 AM
SELECT * does not trigger MR job, while SELECT struct_col.field will, which means the jar is probably available on HS2 host, but not available on the NM hosts. As Naveen mentioned, the class is in hive-hcatalog-xxx.jar, so you can put this jar into Hive AUX directory on HS2 host and then it should be distributed to the cluster while query is running in MR mode. Regarding JsonSerDe in C6.1, Naveen is right and it has been confirmed.
... View more
12-29-2018
12:03 AM
1 Kudo
For others who are using CM, you can go to CM > Hive > Configuration > Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml then enter the new property name and value, save and restart Hive
... View more
12-23-2018
03:41 PM
Hi Matthieu, Are you able to share query PROFILE and enable ODBC driver TRACE logs so that we can see the error in more detail, both from client and server side?
... View more
12-23-2018
03:10 PM
For ODBC related query failure, the info we can check are: 1. Impala query PROFILE, to understand which step failed 2. Impala coordinator log, using the query_id from PROFILE and see where it failed 3. enable TRACE logs on ODBC driver, to see if there is any client side errors : https://www.cloudera.com/documentation/other/connectors/impala-odbc/latest/Cloudera-ODBC-Driver-for-Impala-Install-Guide.pdf search for LogLevel section. In Windows ODBC driver, normally under "Logging Options" button on the configuration window.
... View more