Interesting Sample stage problem
Moderators: chulett, rschirm, roy
Interesting Sample stage problem
I have 2 jobs.
Job1: dataset1 -> copy -> sample - > dataset2
Job2: dataset1 -> sample - > dataset2
Both jobs run fine. However, in Job1, the number of rows moving from dataset1 to copy shows 100 whereas, in Job2, number of rows moving from dataset1 to sample stage shows 20. The source file for both jobs is the same.
Any ideas about this discrepancy? Thanks.
Job1: dataset1 -> copy -> sample - > dataset2
Job2: dataset1 -> sample - > dataset2
Both jobs run fine. However, in Job1, the number of rows moving from dataset1 to copy shows 100 whereas, in Job2, number of rows moving from dataset1 to sample stage shows 20. The source file for both jobs is the same.
Any ideas about this discrepancy? Thanks.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Charter Member
- Posts: 199
- Joined: Tue Jan 18, 2005 2:50 am
- Location: India
This link counts also depends on the stage to which its going...
what is the count it shows when records move from copy stage to sample stage ? I am sure it would be, 20 NOT 100...
I have never observed or noticed such thing in PX, but in server jobs i noticed it many times...
In above design of server job, the hash file had 500 recs but the link count 10 meant number of records from hash file finding a match with the seq file record.
what is the count it shows when records move from copy stage to sample stage ? I am sure it would be, 20 NOT 100...
I have never observed or noticed such thing in PX, but in server jobs i noticed it many times...
Code: Select all
hash File (having 500 records)
|
10
|
seq---1000--> transformer ---> o/p
Shantanu Choudhary
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Max rows per partition = 10 means 20 rows on two partitions.
It's your design - specifically this property - that is limiting the number of rows output from the stage.
You have taken a sample!
It's your design - specifically this property - that is limiting the number of rows output from the stage.
You have taken a sample!
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 83
- Joined: Sat Oct 28, 2006 6:25 am