Discrepency from 8.1 to 8.5v
Moderators: chulett, rschirm, roy
Discrepency from 8.1 to 8.5v
Hi,
I performed inner join and inner join is expected to get match for all business keys from source. The join stage is followed by a transformer for some additional operations. If the invalid source records comes then matching ID will not be found in the join stage and record gets dropped in transformer stage. This code works fine in datastage 8.1v. When we migrated code to datastage 8.5v the records are not getting dropped even the key column is non nullable.
Please help me if there are additional attributes required to set.
I performed inner join and inner join is expected to get match for all business keys from source. The join stage is followed by a transformer for some additional operations. If the invalid source records comes then matching ID will not be found in the join stage and record gets dropped in transformer stage. This code works fine in datastage 8.1v. When we migrated code to datastage 8.5v the records are not getting dropped even the key column is non nullable.
Please help me if there are additional attributes required to set.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
no...
just my job performs join(where i get some id and timestamp based on keys)... followed by transformer where i separate records based on some value....
in that transformer... in 8.1v records are getting dropped for null timestamps...
but in 8.5v records are moving to final dataset even the field is non nullable. They are not getting dropped.
just my job performs join(where i get some id and timestamp based on keys)... followed by transformer where i separate records based on some value....
in that transformer... in 8.1v records are getting dropped for null timestamps...
but in 8.5v records are moving to final dataset even the field is non nullable. They are not getting dropped.
I have just checked v8.1 FP1 vs v8.5 FP1 behaviour - it works exactly the same under my environments (Windows), so:
-Nullable source -> Not-nullable target drops null records (and you see adequate warning message in logs)
-Nullable source -> Nullable target drops null record only when you run data transformation function on the column and are either using v8.1 or have "legacy null processing" turned on
I did my test on timestamp, varchar and integer data types.
Regards
Buzz
-Nullable source -> Not-nullable target drops null records (and you see adequate warning message in logs)
-Nullable source -> Nullable target drops null record only when you run data transformation function on the column and are either using v8.1 or have "legacy null processing" turned on
I did my test on timestamp, varchar and integer data types.
Regards
Buzz