topic Re: tmap error in Talend Studio

tmap error

Anonymous — Thu, 29 Jun 2017 13:00:42 GMT

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

Re: tmap error

cterenzi — Thu, 29 Jun 2017 18:22:56 GMT

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

Re: tmap error

Bluemoon — Thu, 29 Jun 2017 18:49:24 GMT

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

Re: tmap error

Anonymous — Fri, 30 Jun 2017 04:27:32 GMT

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

Re: tmap error

Anonymous — Fri, 30 Jun 2017 07:22:17 GMT

these are the componentsthese are the joins

Re: tmap error

Anonymous — Fri, 30 Jun 2017 07:29:52 GMT

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

Re: tmap error

Anonymous — Fri, 30 Jun 2017 11:56:16 GMT

and also suggest me how to give right outer join in talend tmap component

Re: tmap error

cterenzi — Fri, 30 Jun 2017 14:55:05 GMT

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.

Re: tmap error

Anonymous — Sun, 02 Jul 2017 13:36:16 GMT

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...

Re: tmap error

Anonymous — Sun, 02 Jul 2017 13:47:50 GMT

its not row18 total_quota_before is from row1 and here are the expression builder pics

Re: tmap error

cterenzi — Sun, 02 Jul 2017 19:20:22 GMT

If you attempt to use a field in an expression and one of the values on one of the rows is null, you're going to get null pointer exceptions. You can identify the offending rows by following the guide in the link I posted, or you can make sure you handle nulls in all of your expressions.

Re: tmap error

Anonymous — Sun, 02 Jul 2017 21:27:46 GMT

@cterenzi is correct. You either need to find the fault (find the null ) and prevent it from happening OR you need to put some logic in your expressions to mitigate for nulls.

For example (not using your expressions) if I want to check for a String value of "red" in a column and return a true if it is there AND prevent a null pointer exception I could use the following code in the expression to actively handle the situation where my String column is null

row1.myString!=null ? row1.myString.compareToIgnoreCase("red")==0 : false

The above is an in-line IF and says "If myString is not null AND if it contains 'red' then return true, otherwise return false"

Re: tmap error

vapukov — Mon, 03 Jul 2017 01:44:35 GMT

in additional to all above answers and recommendations

You can balance, where to manage nulls?:

You can manage it in Talend, as many time suggested
or You can manage it by Database

In Your case it could make tMap more clean and not overloaded

For manage nulls by database You can change tMSSQLInput query and add COALESCE function for columns used in tMap formulas

SELECT
    COALESCE(col1,0) as col1,
    COALESCE(col2,0) as col2
FROM table
WHERE
....

I prefer this way, because:
1) as I wrote it make tMap more readable
2) because SQL query it is plain text - I can use text edit with Search/Replace for change prepared query, and it faster than manually edit each tMap element

Note - it not help You in case divide by 0 - this is You need handle right in tMap if necessary

Re: tmap error

Anonymous — Mon, 03 Jul 2017 05:58:44 GMT

Thank you for your support

Re: tmap error

Anonymous — Mon, 03 Jul 2017 06:00:47 GMT

Thank you for your support,I will try it

Re: tmap error

Anonymous — Mon, 03 Jul 2017 06:04:08 GMT

thanks for your support..