Is the output from calculation fields always assumed to be nullable regardless of the setting in the stage? In spite of the fact that all fields had Nullable set to No all the way through the job, was still seeing messages like this:
Code: Select all
Aggregator_1: When checking operator: When binding output interface field "X" to field "X": Converting a nullable source to a non-nullable result; a fatal runtime error could occur; use the modify operator to specify a value to which the null should be converted.
Code: Select all
Modify_14: When checking operator: When binding output schema variable "outRec": When binding output interface field "X" to field "X": Null value handling is specified with a non-nullable source field and no conversion; ignoring.
Is this normal? Is calculation output always considered to be nullable even when I know it will never be and I mark it as such in the job?