tSchemaComplianceCheck : Null rejection while field is Nullable
Hi,
I'm puzzled by tSchemaComplianceCheck behaviour toward null values and schema.
It seems that if the schema is coming from a generic schema, nullable fields are not correctly checked.
Here are the tests :
- one generic schema containing 3 Nullable fields
- a job containing a fixedInputFlow and a tSchemaCompliance check. Both components refer to the same Generic Schema
Test 1:
- input contains a Null value
- "check all columns" is used in tSchemaComplianceCheck
=> the input is rejected.
Test 2
- input contains a Null value
- "check all columns" is unchecked tSchemaComplianceCheck
- the checkbox for the null Check on the 3 columns is activated
=> the input is validated
Test 3 :
- input contains a Null value
- "check all columns" is unchecked tSchemaComplianceCheck
- the checkbox for the null Check on the 3 columns are disabled
=> the input is rejected
I would have expected tests 1 and 2 to validate the input !?
Is it a bug when the "check all columns" is used instead of the column by column check ? Am I missing something ?
Thanks for your help.
Xavier
Indeed, this is same issue. I searched the forum for traces of this bug but forgot to check the Bugtracker... I'll wait for the 3.1.4. version... Thanks. Xavier
