Member since
12-30-2015
73
Posts
3
Kudos Received
4
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1502 | 02-14-2020 11:38 PM | |
1535 | 02-13-2020 02:08 PM | |
2811 | 02-04-2020 10:14 PM | |
2237 | 01-26-2017 10:38 AM |
01-31-2017
04:11 PM
@Lars Volker I thought that way too. Thank you for confirming it 🙂 Gatsby
... View more
01-31-2017
03:52 PM
You might need to click the `cancel` link next to query. Although a query is under exception status, it seems still running and using resources Gatsby
... View more
01-31-2017
03:46 PM
@Lars Volker I have a question for you. Does VIEW still need to load metadata separately even if metadata of TABLE for VIEW is already loaded? @gaurang which CDH/Impala are you using? Thank you Gatsby
... View more
01-31-2017
02:48 PM
Thank you. Then, why does this say that Impala2.8/CDH5.10? http://www.cloudera.com/documentation/enterprise/release-notes/topics/impala_new_features.html#new_features_280
... View more
01-31-2017
01:42 PM
Hi, I noticed that CDH5.10 is realesed and has Impala 2.8. However, it seems there are not Impala 2.8 RPM packages for RedHat6. Can you tell me where I can them? Thank you Gatsby
... View more
Labels:
- Labels:
-
Apache Impala
01-26-2017
10:38 AM
I found out what caused this issue in this case. Nodes have different Impala version, such as 2.8, 2.4 etc. The interesting thing is that `compute stats` operation didn't work if run in Impala 2.8, but the operation works in Impala 2.4. Anyway, I hope this can help you solve your problem. Thank you Gatsby
... View more
01-25-2017
05:11 PM
Is this related to kerberos authentication??
... View more
01-12-2017
06:18 PM
Hello, Today, when I run "compute stats" command in Impala, I got this kind of error. Can you tell me what I need to check to root-cause the issue? I've restart Impala cluster in case, but still doesn't work. Thank you Gatsby Query (id=e14f8e09bc61152e:edb3c88b00000000):
Summary:
Session ID: ec4783541c02a53b:94e307a26bcc719e
Session Type: BEESWAX
Start Time: 2017-01-12 17:17:13.717774000
End Time: 2017-01-12 17:17:14.027669000
Query Type: DDL
Query State: EXCEPTION
Query Status: ExecPlanRequest rpc query_id=fb4b42b5b270a117:f7b20fe800000000 instance_id=fb4b42b5b270a117:f7b20fe800000001 failed: RPC Error: No more data to read.
Impala Version: impalad version 2.8.0-cdh5-INTERNAL RELEASE (build )
User: root
Connected User: root
Delegated User:
Network Address: ::ffff:10.168.16.16:44184
Default Db: default
Sql Statement: compute STATS onlinemarketing_201701
Coordinator: hadoop2-wn2.dwarehouse.internal:22000
Query Options (non default):
DDL Type: COMPUTE_STATS
: 0.000ns
Query Timeline: 310.440ms
- Start execution: 68.354us (68.354us)
- Planning finished: 2.602ms (2.533ms)
- Request finished: 265.917ms (263.315ms)
- Unregister query: 309.901ms (43.983ms)
ImpalaServer:
- ClientFetchWaitTimer: 0.000ns
- RowMaterializationTimer: 0.000ns
... View more
Labels:
- Labels:
-
Apache Impala
03-14-2016
09:44 PM
what if I only open less than 50 partitions out of 1M at any given time??
... View more
02-23-2016
12:31 AM
1 Kudo
Jeff, I understand what you explained. However, what if HDFS rebalances data automatically? If this scenario, it seems there is only one option left using INVALIDATE METADATA.
... View more