[ 
https://issues.apache.org/jira/browse/HIVE-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296178#comment-14296178
 ] 

Xuefu Zhang edited comment on HIVE-9503 at 1/29/15 1:01 AM:
------------------------------------------------------------

Yeah, Hive has long reached to a point where the properties are confusing and 
sometimes contradicting and duplicating. These two properties plus 
hive.auto.convert.join are an example. The two properties are meant to be used 
together. Ignoring one while taking the other doesn't seem to be a clean 
solution. While it's already a legacy for MR and Tez, I'd like to have a 
cleaner solution for Spark since we still have the chance. If we want to be 
consistent across engines, I'd rather fix Spark to be consistent with MR.


was (Author: xuefuz):
Yeah, Hive has long reached to a point where the properties are confusing and 
sometimes contradicting and duplicating. These two properties plus 
hive.auto.convert.join are an example. The two properties are meant to be used 
together. Ignoring one while taking the other doesn't seem to be a clean 
solution. While it's already a legacy for MR and Tez, I'd like to have a 
cleaner solution for Spark since we still have the chance. 

> Update 'hive.auto.convert.join.noconditionaltask.*' descriptions
> ----------------------------------------------------------------
>
>                 Key: HIVE-9503
>                 URL: https://issues.apache.org/jira/browse/HIVE-9503
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Szehon Ho
>            Priority: Minor
>
> 'hive.auto.convert.join.noconditionaltask' flag does not apply to Spark or 
> Tez, and only to MR (which has the legacy conditional mapjoin)
> However, 'hive.auto.convert.join.noconditionaltask.size' flag does apply to 
> Spark, Tez, and MR, even though the description indicates it only applies if 
> the above flag is on, which is true only for MR.
> These configs should be updated to reflect this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to