[
https://issues.apache.org/jira/browse/HADOOP-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543333
]
udanax edited comment on HADOOP-2021 at 11/17/07 7:32 PM:
---------------------------------------------------------------
But, Can not insert duplicate key row in hbase table.
so........
{code}
r3
a b c e f
==============================
row1.row1 a1 b1 c1 e1 a1
row1.row4 a1 b1 c1 e4 a1
{code}
Then, Can i get a r1.row set or r2.row set??
hmm.
Also, is it all right in theory ??
If you have any ideas, let me know.
was (Author: udanax):
But, Can not insert duplicate key row in hbase table.
so........
{code}
r3
a b c e f
==============================
row1.row4 a1 b1 c1 e1 a1
row1.row4 a1 b1 c1 e4 a1
{code}
Then, Can i get a r1.row set or r2.row set??
hmm.
Also, is it all right in theory ??
If you have any ideas, let me know.
> 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.
