Transformer output counts not totalling input count
Moderators: chulett, rschirm, roy
Transformer output counts not totalling input count
I have a job with a transformer which takes in 907,124 rows.
it has two outputs, both with constraint on non null char(1) column.
The 1st has constraint input.colX='5'
The other has constraint input.colX <> '5'
The output counts are 814,682 and 60,142 respectively, which add up to 874,824.
This is a difference of 32,300 rows compared with input rows.
There are no rejects. What can have happened to the other rows?
As a workaround I was thinking I could use just one of the constraints and mark the other as a reject rows constraint, but I wouldnt know which one of the = or <> is processing the correct number of rows.
Any ideas?
it has two outputs, both with constraint on non null char(1) column.
The 1st has constraint input.colX='5'
The other has constraint input.colX <> '5'
The output counts are 814,682 and 60,142 respectively, which add up to 874,824.
This is a difference of 32,300 rows compared with input rows.
There are no rejects. What can have happened to the other rows?
As a workaround I was thinking I could use just one of the constraints and mark the other as a reject rows constraint, but I wouldnt know which one of the = or <> is processing the correct number of rows.
Any ideas?
Re: Transformer output counts not totalling input count
dzdiver wrote:I have a job with a transformer which takes in 907,124 rows.
it has two outputs, both with constraint on non null char(1) column.
The 1st has constraint input.colX='5'
The other has constraint input.colX <> '5'
The output counts are 814,682 and 60,142 respectively, which add up to 874,824.
This is a difference of 32,300 rows compared with input rows.
There are no rejects. What can have happened to the other rows?
As a workaround I was thinking I could use just one of the constraints and mark the other as a reject rows constraint, but I wouldnt know which one of the = or <> is processing the correct number of rows.
Any ideas?
Check the LOg in Director .. may be due to Nulls
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The nullable property is purely documentary within DataStage. It enforces nothing.
It serves as a valuable check for developers not to allow nulls to get through to columns in target tables that are defined to be not null.
It serves as a valuable check for developers not to allow nulls to get through to columns in target tables that are defined to be not null.
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: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: