Member since
11-12-2014
25
Posts
2
Kudos Received
4
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1704 | 12-02-2015 05:50 PM | |
3575 | 12-02-2015 05:42 PM | |
1300 | 12-17-2014 04:23 PM | |
2204 | 11-12-2014 06:10 PM |
10-24-2016
01:24 PM
The connection to HMS seems to be working fine. Here are some things to consider: 1. create a table in Hive and run invalidate metadata in Impala. Does this work? 2. Check the impalad.INFO and catalogd.INFO for any exceptions/errors 3. Keep in mind that invalidate metadata is asynchronous, i.e. it returns immediately and then in the background the catalog objects are sent to the impalad nodes. This could take some time, so the question is if the db shows up eventually (after a few secs) or never. Dimitris
... View more
12-02-2015
05:50 PM
Hi Zhifeng, I apologize for the late response. Impala currently only supports SELECTS and INSERTS in HBase tables. Unfortunately, all the other features you mention are not supported. Regards, Dimitris
... View more
12-02-2015
05:42 PM
Hi Mauricio, You're probably running into IMPALA-1480. If a table has a substantial number of partitions (>10K) it take a long time to perform certain DDL operations even though only a small fraction of metadata changes. Dimitris
... View more
12-17-2014
04:23 PM
Impala 2.0 does not support nested types. It is in Impala's roadmap and will be added in a future release. Dimitris
... View more
11-25-2014
10:03 AM
I meant the query profile of query you run in Impala 2.0 by setting MEM_LIMIT=15G. Just post the section with the estimated/peak memory usage per node. Is it the same profile as the one you posted earlier? Dimitris
... View more
11-25-2014
09:29 AM
Hi, The explain is not really usefull for identifying the memory offenders. Can you post the output of profile (http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_explain_plan.html#perf_profile_unique_1) after you've run the query? That will shed some light on the actual memory requirements of each execution node in your query. Thanks Dimitris
... View more
11-24-2014
11:26 AM
Hi, Quick question. Do you have statistics in the tables you're querying? It doesn't look like it. Can you run compute stats and see if the problem persists. Also, the log messages you posted are just warnings. The problem is not with the scan nodes but with the computation of the hash join. Dimitris
... View more
11-22-2014
09:19 AM
Hi, Is the query that is failing running in isolation or are other workloads running at the same time? Can you post the profile information for that query and any relevant sections from the impalad log? Dimitris
... View more
11-12-2014
06:10 PM
1 Kudo
The problem is with the following predicate in the where clause "where a11.partition_date = a12.partition_date = 20140411". The condition a12.partition_date = 20140411 is not properly pushed to the scan node of a12, hence no partition pruning is happening. You may want to rewrite it as "a11.partition_date = a12.partition_date and a12.partition_date = 20140411". Dimitris
... View more