[
https://issues.apache.org/jira/browse/HIVE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841414#action_12841414
]
He Yongqiang commented on HIVE-1194:
------------------------------------
@namit,
498's join results is in the results:
496 val_496 496 val_496
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
498 val_498 498 val_498
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
5 val_5 5 val_5
9 val_9 9 val_9
I will add a automatic check query in the test and upload a new one.
> 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, hive-1194-2010-3-3-2.patch, hive-1194-2010-3-3.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.
