Join Stage - Paritionning question
Posted: Thu Jun 08, 2006 5:51 am
Hi.
I have a question about jobs that contains multiple join stages and their partition...
Actually, I have a PX job that contains 2 join stages (left outer join). I've set the partitionning on both stages to Hash...
The first Join has 5 keys... Key1,Key2,Key3,Key4,Key5 on the two input links. I used these keys for partitionning as well.
The second has 4 keys... the keys of the partition is a subset of the first join... Key1,Key2,Key3,Key4 (these keys are used for both, partitionning and key of the join).
It seems that if I do not check the option Perform sort on the second join stage... it does not find the corresponding record in the right part of the join (but it is there and the key definition is good)...
In other jobs, I use to have more than one join stage... but they don't have the same keys... So I didn't need to check this option on... and it always worked fine...
This is weird... I tough by partitionning correctly the join stage, it should always work fine??? Is this a Datastage bug???
Thanks.
Math
I have a question about jobs that contains multiple join stages and their partition...
Actually, I have a PX job that contains 2 join stages (left outer join). I've set the partitionning on both stages to Hash...
The first Join has 5 keys... Key1,Key2,Key3,Key4,Key5 on the two input links. I used these keys for partitionning as well.
The second has 4 keys... the keys of the partition is a subset of the first join... Key1,Key2,Key3,Key4 (these keys are used for both, partitionning and key of the join).
It seems that if I do not check the option Perform sort on the second join stage... it does not find the corresponding record in the right part of the join (but it is there and the key definition is good)...
In other jobs, I use to have more than one join stage... but they don't have the same keys... So I didn't need to check this option on... and it always worked fine...
This is weird... I tough by partitionning correctly the join stage, it should always work fine??? Is this a Datastage bug???
Thanks.
Math