Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
when I run the job it starts perfectly but in between it stops and gives null pointer exception
what should I do plz any one help me
thanks in advance
This is usually an indication that one of the expressions in your tMap uses a schema value in a way that doesn't handle null values. This guide by our own @rhall walks through the steps of creating an error output in a tMap component that will show you which row(s) cause the error:
https://www.rilhia.com/quicktips/quick-tip-how-debug-tmap-errors
This is usually an indication that one of the expressions in your tMap uses a schema value in a way that doesn't handle null values. This guide by our own @rhall walks through the steps of creating an error output in a tMap component that will show you which row(s) cause the error:
https://www.rilhia.com/quicktips/quick-tip-how-debug-tmap-errors
In general, you get null pointer exception tMap if your performing any string operations on null data like (<string>.split(",")) [If this is case can handle the null by following syntax <string> != null ? <string>.split(",") : null] one of the use-case, if possible please share the tMap screenshot for more accuracy
Hello,
Could you please post your current job setting screenshots on forum which will be helpful for us to address your issue?
Best regards
Sabrina
these are the components
these are the joins
there are 5 customer tables with different aliases
row3;c.customer
row7:cs.customer
row11:dc.customer
row12c.customer
row19:scu.customer
and two similar tables with different aliases
src.pin_config
drs.pin_config
and two cell_location tables with aliases
cla.cell_location
clc.cell_location
and also suggest me how to give right outer join in talend tmap component
If all those tables are in the same database, would it not make more sense to do the joins on the database side?
To address your original issue, it looks like there are two tMap output field that use a formula: SOURCE_BALANCE_B... and DESTINATION_BALANCE...
To avoid null pointer exceptions, you'll probably want to check each field used for nulls and set an appropriate result for that case. (e.g. row18.TOTAL_QUOTA_BEFORE == null ? 0 : <your formula here>) If you show the entire expression, we can help write the expression to handle nulls for all fields involved.
row18.total_quota_before==null?0:<which formula to be used here> l'm not getting
you want to see formula in the expression builder...
its not row18 total_quota_before is from row1 and here are the expression builder pics