[
https://issues.apache.org/jira/browse/HADOOP-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543362
]
udanax edited comment on HADOOP-2021 at 11/18/07 2:02 AM:
---------------------------------------------------------------
On second thought, I changed the result format.
And I had decision to store the join result as describe below.
Thanks, jimk and stack.
but, if you find an errors or inconsistencies, let me know.
{code}
r3
r1.row a b c r2.row e f
=============================================
row1.row1 row1 a1 b1 c1 row1 e1 a1
row1.row4 row1 a1 b1 c1 row2 e4 a1
{code}
was (Author: udanax):
On second thought, I changed the result format.
And I had decision to store the join result as describe below.
Thanks, jimk and stack.
but, if you find a errors or inconsistencies, let me know.
{code}
r3
r1.row a b c r2.row e f
=============================================
row1.row1 row1 a1 b1 c1 row1 e1 a1
row1.row4 row1 a1 b1 c1 row2 e4 a1
{code}
> Sort Join Implementation
> ------------------------
>
> Key: HADOOP-2021
> URL: https://issues.apache.org/jira/browse/HADOOP-2021
> Project: Hadoop
> Issue Type: Sub-task
> Components: contrib/hbase
> Affects Versions: 0.14.1
> Environment: all environments
> Reporter: Edward Yoon
> Priority: Minor
> Fix For: 0.16.0
>
> Attachments: 2021_v01.patch
>
>
> If we don't have an index for a domain in the join, we can still improve on
> the nested-loop join using sort join.
> {code}
> R1 = table('movieLog_table');
> R2 = table('stockCompany_info');
> result = R1.join(R1.studioName = R2.corporation) and R2;
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
