My job returned the message
When checking operator: When validating export schema: At field "inputcol": Exporting nullable field without null handling properties
I inserted a modify stage and tried both NullToValue and handle_null functions but still receive the same error. I have made a copy of the job and applied both in a transformer stage but still in vain.
Can anybody advise on where I am going wrong?
The method used is inputcol = handle_null(inputcol, 0) and
inputdesc = handle_null(inputdesc, "NULL")
Same as NullToValue in place of handle_null.
NULL trapping
Moderators: chulett, rschirm, roy
Willkommen, NewPXUser.
good job in trying to use different methods to debug your problem! I think the cause might not lie in the actual data itself but in the meta-definitions within the job. What database/stage are you writing to and in which stage is the error message generated? I am fairly certain that if you change your output to a PEEK, sequential or fileset the error will go away (it won't be solved, but you'll be a step further towards solution).
good job in trying to use different methods to debug your problem! I think the cause might not lie in the actual data itself but in the meta-definitions within the job. What database/stage are you writing to and in which stage is the error message generated? I am fairly certain that if you change your output to a PEEK, sequential or fileset the error will go away (it won't be solved, but you'll be a step further towards solution).
</a>
Hi,
It is about the metadata and not about the data. The data might not be null or blank but the metadata might have the nullability set to YES.
If you are using modify stage use the following syntax
output_column=handle_null(input_column, value instead of null)
If you want the warning to be avoided when using sequential file stage then set the nullablity option that can be found in field properties column.
HTH
--Rich
Pleasure in job brings perfection in work
It is about the metadata and not about the data. The data might not be null or blank but the metadata might have the nullability set to YES.
If you are using modify stage use the following syntax
output_column=handle_null(input_column, value instead of null)
If you want the warning to be avoided when using sequential file stage then set the nullablity option that can be found in field properties column.
HTH
--Rich
Pleasure in job brings perfection in work
Yes. You were correct. The 'Nullable' property was set to 'Yes'. On making it to 'No', the warning disappeared.
Having said that, the error appear to be misleading (atleast for people like me). It says
When checking operator: When validating export schema: At field "inputcol2": Exporting nullable field without null handling properties
but I had 'null handling properties' in place by NullToValue / handle_null.
Infact if I remove the null handling routine in the tx stage, the job still works without the warning !! The input has columns to be Nullable whereas the output says 'No' to it.
Having said that, the error appear to be misleading (atleast for people like me). It says
When checking operator: When validating export schema: At field "inputcol2": Exporting nullable field without null handling properties
but I had 'null handling properties' in place by NullToValue / handle_null.
Infact if I remove the null handling routine in the tx stage, the job still works without the warning !! The input has columns to be Nullable whereas the output says 'No' to it.
That warning message said it exactly: If your metadata is nullable, and you're attempting to write to a flat file without handling it by means of something like "Null Field Value" on "Field defaults", then you will get a warning, even though you may not have any data with NULL.
Next time: Ensure that there's no nullable fields, OR provide the operator with a way to handle NULL.
Next time: Ensure that there's no nullable fields, OR provide the operator with a way to handle NULL.