null handling in transformer/join stages
Posted: Thu Dec 24, 2009 2:53 am
Hi,
I have a job where i read the records from dataset, sort using sort stage, join with a table, then add some extra columns in a transformer and insert the records in the target Oracle table.
Even if there are null values in the input columns, i just pass it as it is to the output table.
do i need to do any null handling before inserting..i see in some of the existing jobs that they have done something like If isnull(col) then setnull else col.
but i dont see a need of it..i dont see any reject records because of null values in some of the columns, but want to check if it is a best practice to do that.
I have a job where i read the records from dataset, sort using sort stage, join with a table, then add some extra columns in a transformer and insert the records in the target Oracle table.
Even if there are null values in the input columns, i just pass it as it is to the output table.
do i need to do any null handling before inserting..i see in some of the existing jobs that they have done something like If isnull(col) then setnull else col.
but i dont see a need of it..i dont see any reject records because of null values in some of the columns, but want to check if it is a best practice to do that.