You are not logged in.
I think the following is a bug and I submit it to you guys.
In the following simple job I have a tMap where it's input are DWH (Data Warehouse dimension table) and POMS (source table). The job works when there are records on the DWH table but gives a Null pointer exception when the amount of records is 0 (table empty). Shouldn't the main row be rejected based on the tmap settings and captured in the create output?
I know that the null pointer is related with the empty resultset.
I think i found the cause of this error.
The only case where I reproduced the error is when I set the column "row6.newKey" as Integer, I can't see it on your screenshot.
In my point of view you should only set your column "Var.Numeric" as Integer also by checking nullable. Indeed when no lookup row matches for table "row2", "row6.newKey" become null, but "Var.Numeric" can't be set with a null value, then it occurs NullPointerException.
I hope this solution will resolve your problem ;-)
I agree with you, I need your ideas on this subject, I created the [Bugtracker, bug 1800, fixed] Search a performant and smart solution to inform users that null values can't be set in primitive types when case happens to support it.