If I remove nullable property for Col_One, that row is getting rejected if it has null. Again, Col_one is integer.
So, If I pass in a null or a string in Col_one it is rejecting successfully. I am just getting a warning in the log saying that import error and no default value.
Samething does not work for a string filed. If I pass in 123 in the string field it does not reject, probably because the number is read in as a string as this is a flat file. But for nulls, the row is not getting rejected
Null handling in schema file
Moderators: chulett, rschirm, roy
I found a work around, I had to add a filter stage after the sequential file stage and specify the where condition is not null for each of the not nullable columns.
Ofcourse, this works as I know the not nullable column names. But for a truely dynamic metadata scenario I don't know how this would work. This is probably one of those things that Datastage has a problem to deal with.
Thank you all for the help.
Ofcourse, this works as I know the not nullable column names. But for a truely dynamic metadata scenario I don't know how this would work. This is probably one of those things that Datastage has a problem to deal with.
Thank you all for the help.