In the lookup stage, I am doing range lookup on the Version From and To dates in the table with a date field(appl date) comes out of join stage.
I have the Version from and to dates and the appl date all defined as nullable in the table definition. I understand that these fields can't be NULL and we are correcting it but why would it give such a warning ?
and then failed with the error :When checking operator: When binding input interface field "VERSION_FROM_DATE" to field "VERSION_FROM_DATE": Converting a nullable source to a non-nullable result;
a fatal runtime error could occur;
use a modify operator to specify the value to which the null should be converted.
So, I had changed sql in DB2 connector stage to give a default value if version from and to dates are null. Now the job does not fail but I still have the same warning.Null in field "VERSION_FROM_DATE "; the result is non-nullable
and there is no handle_null to specify a default value.
Null in field "VERSION_TO_DATE "; the result is non-nullable
and there is no handle_null to specify a default value.
My questions are:
1. Why would it throw above warning and the error when all those fields are nullable ?
Is it because those fields are used in the range lookup ?
2. How can I get rid of the warning message ?