Support Questions

AmitAdhau · ‎03-29-2017

Hi,

I had a cluster[CDH 5.8.2] in which I was using Impala and Kudu.

Impala Parcel is downloaded from - http://archive.cloudera.com/beta/impala-kudu/parcels/latest/

I have upgraded this cluster to CDH 5.10 with cloudera manager 5.10.

Now, running the select verison() query on this upgraded cluster in Impala gives me below details;

impalad version 2.7.0-cdh5.10.0 RELEASE

However, in CDH 5.10 upgrade they mentioned the support for Imapal 2.8. I can not find the parcel for the Impala 2.8.

Also, running the delete command on Impala table give me below error.

"ERROR: AnalysisException: Impala does not support modifying a non-Kudu table: default.impala_testtable"

Questions:

1. Can anybody suggest me how can I upgrade to Impala 2.8? Is there any parcel for the same or the one which I'm currently using is the latest?

2. As running delete command on Impala table gives me the error what is the alternative to delete data from existing impala table? However, the delete command works fine with Kudu tables.

Can anybody please help me on the same.

Thanks,

Amit

Lars Volker · ‎03-29-2017

Hi Amit,

Your first question has already been discussed in this thread:

There's a bit of a story there. When we started preparing the 5.10 CDH release, the Apache 2.8 Impala release was not ready, so we had to call it "Impala 2.7" in the version number. Impala 2.8 was officially released after we finished putting together the CDH5.10 release - too late to bump the version in all places.

CDH5.10 Impala is almost exactly the same as 2.8, plus or minus a few patches, so in most of the announcements we've just called it 2.8.

You can find a full list of commits in CDH5.10.0 here: https://github.com/cloudera/Impala/commits/cdh5-2.7.0_5.10.0

The full list of commits in Impala 2.8 are here: https://github.com/apache/incubator-impala/commits/branch-2.8.0

To your second question: Impala does indeed not support the DELETE command for non-Kudu tables. You can use the TRUNCATE command to completely delete all data in a table.

Cheers, Lars

View solution in original post

AlonEldi · ‎04-05-2017

Hi Lars , Tim

Coputing stats on specific partion works as it should in 5.10 and seesm to fix the problem .

5.10 with inc_stats_size_limit_bytes = 1073741824 ( 1GB)

[gc-test-impala28-02.c.bi-environment-1271.internal:21000] > COMPUTE INCREMENTAL STATS dwh.dwh_events partition (cluster_id=11,day=20170401);
Query: compute INCREMENTAL STATS dwh.dwh_events partition (cluster_id=11,day=20170401)
+-------------------------------------------+
| summary |
+-------------------------------------------+
| Updated 1 partition(s) and 382 column(s). |
+-------------------------------------------+
Fetched 1 row(s) in 2.23s

5.9

-------

[gc-dp-pdpprd-data-04.c.bi-environment-1271.internal:21000] > COMPUTE INCREMENTAL STATS test_partitions.dwh_events partition (cluster_id=11,day=20170401);
Query: compute INCREMENTAL STATS test_partitions.dwh_events partition (cluster_id=11,day=20170401)
ERROR: AnalysisException: Incremental stats size estimate exceeds 200.00MB. Please try COMPUTE STATS instead.

Many Thanks 🙂

Alon

thewayofthinkin · ‎04-24-2017

Yeap, you're right

Lars Volker · ‎04-04-2017

Thank you for catching this Tim!

The "SORTBY()" hint was added in IMPALA-4163, which was not included in Impala 2.8.0. It is currently being reworked into a SQL clause (IMPALA-4166), so I cannot make promises as to which release will contain this feature. My apologies for the confusion. I will make sure the documentation gets updated.

Cloudera Community

Support Questions

Impala 2.8 vs 2.7 on CDH 5.10 upgrade