Problem with entire partitioning in lookup
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 103
- Joined: Wed Jul 06, 2005 12:29 am
Problem with entire partitioning in lookup
When I select entire partitioning in lookup and I have got 4 nodes with 4 matching rows I get the ouptut of 16 rows as it process all the data in each node.How to avoid this and get only 4 records.
Re: Problem with entire partitioning in lookup
select round robin.....RAJEEV KATTA wrote:When I select entire partitioning in lookup and I have got 4 nodes with 4 matching rows I get the ouptut of 16 rows as it process all the data in each node.How to avoid this and get only 4 records.
rjhcc
-
- Participant
- Posts: 103
- Joined: Wed Jul 06, 2005 12:29 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
-
- Participant
- Posts: 467
- Joined: Tue Mar 20, 2007 6:36 am
- Location: Chennai
- Contact:
Even when the input partitioning is round robin?ray.wurlod wrote:The best partitioning for lookup is identical partitioning to the stream input. ...
Partition both the input and the reference links using the Hash partitioning method on the key columns. This should fix your problem of getting duplicates in the output.
Minhajuddin
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: