Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 07-01-2019 11:06 AM - edited 09-16-2022 07:29 AM
I have enable stats using `COMPUTE STATS` on a table. After this when I re-run the query, it's giving me an error `A RIGHT OUTER JOIN type with no equi-join predicates can only be executed with a single node plan`. Dropping the stats is execuring the query. I'm trying to improve the query performance.
Created 07-02-2019 03:16 PM
By default, Impala uses something called as a “broadcast join” which assumes that the left table is larger than the right. Which is not true in my case.
It does the join inversion inherently if this is not done in the query.
When such an inversion is to be overridden, it is suggested to be overriden by the keyword “STRAIGHT_JOIN“.
Or re-write the query to swap the join sets and make the left join a right join.
Since in this case it’s non-equi join, right outer joins do not support a right outer join in Impala yet. Replaced the left join with an INNER JOIN and swapping the datasets.
Created 07-01-2019 04:31 PM
Created 07-02-2019 03:16 PM
By default, Impala uses something called as a “broadcast join” which assumes that the left table is larger than the right. Which is not true in my case.
It does the join inversion inherently if this is not done in the query.
When such an inversion is to be overridden, it is suggested to be overriden by the keyword “STRAIGHT_JOIN“.
Or re-write the query to swap the join sets and make the left join a right join.
Since in this case it’s non-equi join, right outer joins do not support a right outer join in Impala yet. Replaced the left join with an INNER JOIN and swapping the datasets.
Created 07-15-2019 08:37 AM
You shouldn't be seeing this error. I think you are probably hitting an old bug where sometimes an invalid execution plan was generated. - https://issues.apache.org/jira/browse/IMPALA-5689 or https://issues.apache.org/jira/browse/IMPALA-3063
It should be fixed in CDH5.13.0 or later.
Created 07-15-2019 01:52 PM
Probably, the version we are using is 5.12.