No, as CDH 5.7 includes Hive 1.1.0 plus backported fixes. But HPL/SQL is also available as a separate download and claims to work with any Hive version per their download page: http://www.hplsql.org/download ... View more

Great thanks for your answer. ... View more

Indeed there is, and the issue has been fixed! See: https://issues.cloudera.org/browse/IMPALA-2974   You can work around that specific problem in Impala by using the following syntax.   ALTER TABLE A REPLACE COLUMNS (complete list of column definitions)   My apologies for the inconvenience. ... View more

You can create a 1-row dummy table like this:   select 1 id, 'a' d from (select 1) dual where 1 = 1   You also have to rewrite the query to avoid an uncorrelated not exists. You can do something like:   select 1 id, 'a' d from (select 1) dual where (select count(*) from employee where empid > 20000) = 0   Computing the count might be expensive so you could add a limit like   select 1 id, 'a' d from (select 1) dual where (select count(*) from (select id from employee where empid > 20000 limit 1) emp) = 0 ... View more

Yes, Impala is throwing that error. Impala has a few hard limitations on (1) the number of children an expression can have and (2) the depth of the expression tree.   You can typically work around the problem by rephrasing the huge expression as a join on a new table. For example, in your example, you'd have something like:   create table grid {   lat_lower_bound double,   lat_upper_bound double,   long_lower_bound double,   long_lower_bound }   and then   select ... from original_table t, grid g where t.longitude between g.lat_lower_bound and g.lat_upper_bound   and t.latitute between g.long_lower_bound and g.long_upper_bound   ... View more

Ah, I got it.   Tmr, I will try to compare the difference between first and second run by checking exec summary.   MANY Thank you.   ... View more

Yea :). Thanks everyone for your reports and JIRA contricutions! ... View more