[
https://issues.apache.org/jira/browse/HIVE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840802#action_12840802
]
Namit Jain commented on HIVE-1194:
----------------------------------
smb_mapjoin4.q:
POSTHOOK: query: select /*+mapjoin(a,b)*/ * from smb_bucket_1 a left outer join
smb_bucket_2 b on a.key \
= b.key left outer join smb_bucket_3 c on b.key=c.key
POSTHOOK: type: QUERY
POSTHOOK: Input: defa...@smb_bucket_2
POSTHOOK: Input: defa...@smb_bucket_3
POSTHOOK: Input: defa...@smb_bucket_1
POSTHOOK: Output:
file:/Users/heyongqiang/Documents/workspace/Hive-Test/build/ql/scratchdir/hive_2010-03\
-02_16-28-42_346_3202067314016412424/10000
1 val_1 NULL NULL NULL NULL
3 val_3 NULL NULL NULL NULL
4 val_4 NULL NULL NULL NULL
5 val_5 NULL NULL NULL NULL
10 val_10 NULL NULL NULL NULL
I am not sure if the above semantics are correct - this may be a existing bug
in the code, can you check the semantics of mysql and oracle ?
> sorted merge join
> -----------------
>
> Key: HIVE-1194
> URL: https://issues.apache.org/jira/browse/HIVE-1194
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: He Yongqiang
> Fix For: 0.6.0
>
> Attachments: hive-1194-2010-02-28.patch, hive-1194-2010-3-2.2.patch,
> hive-1194-2010-3-2.patch
>
>
> If the input tables are sorted on the join key, and a mapjoin is being
> performed, it is useful to exploit the sorted properties of the table.
> This can lead to substantial cpu savings - this needs to work across bucketed
> map joins also.
> Since, sorted properties of a table are not enforced currently, a new
> parameter can be added to specify to use the sort-merge join.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
