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

Ashutosh Chauhan commented on HIVE-3403:
----------------------------------------

Make sense. I am not suggesting to include all that in this jira, but wanted to 
make sure we are on same page as to where are heading.
Though, w.r.t, configs I can see your point about adding more configs, but I 
still think by default optimization configs should be on. Whole point of 
release is to ship stable codebase. By definition trunk is not considered 
stable (as stable as in making release out of it), so time we get between 
committing to trunk and releasing is for stablizing new codebase, but if by 
default configs are off, bugs lurking in new codebase will never be exposed.  
                
> user should not specify mapjoin to perform sort-merge bucketed join
> -------------------------------------------------------------------
>
>                 Key: HIVE-3403
>                 URL: https://issues.apache.org/jira/browse/HIVE-3403
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3403.10.patch, hive.3403.11.patch, 
> hive.3403.12.patch, hive.3403.13.patch, hive.3403.14.patch, 
> hive.3403.15.patch, hive.3403.16.patch, hive.3403.17.patch, 
> hive.3403.18.patch, hive.3403.19.patch, hive.3403.1.patch, 
> hive.3403.21.patch, hive.3403.22.patch, hive.3403.23.patch, 
> hive.3403.24.patch, hive.3403.25.patch, hive.3403.26.patch, 
> hive.3403.2.patch, hive.3403.3.patch, hive.3403.4.patch, hive.3403.5.patch, 
> hive.3403.6.patch, hive.3403.7.patch, hive.3403.8.patch, hive.3403.9.patch
>
>
> Currently, in order to perform a sort merge bucketed join, the user needs
> to set hive.optimize.bucketmapjoin.sortedmerge to true, and also specify the 
> mapjoin hint.
> The user should not specify any hints.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to