I am implementing the SCD on table ,so I am taking the max value of that column at the start of the job and storing it in the context variable (X),which i declared as int .Now that context variable i am assigning in the numeric sequence as " Numeric.sequnce('s1',X,1) ".
Though I get above warning in 7.1 DI I am able to load data into the table.The problem arises when I load multiple tables in the same job and use tdie component ,the job will stopped instead of loading the next table.
If i run the same job in talend 6.4 DI ,I am not getting any warning and able to load the data successfully.
Can anyone please help me how to avoid this warning in 7.1 DI.
Thanks & Regards,
I am taking the max value of the column at the start of the job and storing it in the context variable (X),which i declared as int .Now that context variable i am assigning in the numeric sequence as " Numeric.sequnce('s1',X,1) " while loading the same column in table.
The same job is working fine in talend 6.4 DI ,but when comes to 7.1 DI ,it is throwing below warning.
"Null value will be used for context parameter X: For input string: "context.X"
Thanks & Regards.
Please find attached screenshots of the same job which is getting warning in talend 7.1 DI and not getting warning in talend 6.4 DI .
I am taking SOURCE_ID from STG_SOURCE table and assigning this SOURCE_ID to context variable (context.SOURCE_ID) .
I am using this context.SOURCE_ID to load one column in output table. Data is loading properly ,but I am getting this warning "Null value will be used for context parameter SOURCE_ID: For input string: "context.SOURCE_ID"
Thanks & Regards,
I'm facing the same problem after moving from Talend 7.0.1 to Talend 7.1.1 with BigDecimal parameters in context definitions.
As far as I've been able to see, the problem comes from the default value in the context itself. Previously, if a BigDecimal parameter had no value attached in its context definition, it translated as a null value (a correct value for BigDecimal). Now, any value put as default for the context parameter is taken as a String value, so no value is translated to empty String (""), which is not a valid BigDecimal value.
As it says in the warning, the job itself changes the empty string for a null value, so it works. However, it prints the "error" in every iteration, so it's really annoying. I'm still trying to see if I can deactivate this alert somehow (if I'm not able to make the context BigDecimal parameter understand the empty value as null instead of "").
I've just fixed it thanks to the next workaround.
I've had to edit the file ParserUtils.java (<TalentFolder>\plugins\org.talend.librariesmanager_188.8.131.5281026_1147\resources\java\routines\system)
So it changed from this:
And that made the trick.
(However, I think the problem came from how the context deals with empty values)
Any suggestion from our Talend expert? A patch maybe?
We have the same problem as JoanBenz, but with Integer, not BigDecimal.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables