Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I created a Talend job which imports data from a SQL database into a TMS database.
During this job, a varchar field is translated into an integer field. This is done in two steps: First I check if the varchar field is an Integer and if it's true, I convert it, else it becomes 0 (zero).
To do this, a piece of code is used:
This is in my tMap:
I created the job with Talend 5.1.2.r90681 and tested it on Windows 7.0. A random record says '001554' in SQL. After conversion the field is saved as 1554 in the TMS database.
I exported the job and extracted the zip file on a Linux system. (Nothing special, I have done this before for around 40 jobs).
And now the strange thing: After running the job on Linux, the same record is converted to 15 instead of 1554.
Why???
Edit:
It only effects records with leading zero's. Records without leading zero's are converted in the correct way.
(Example given: '002534' is converted wrongly to 25. '2534' is converted to 2534.)
Screenshots: First subjob clears the output database. The second subjob retrieves information from a SQL server, convert some fields and store the result in the output database Kewill.
During this job, a varchar field is translated into an integer field. This is done in two steps: First I check if the varchar field is an Integer and if it's true, I convert it, else it becomes 0 (zero).
To do this, a piece of code is used:
package routines;
public class MyRoutines {
public static Boolean isNumeric(String str) {
if(str.equals("")){ return false; }
for(int i=str.length();--i>=0;){
int chr=str.charAt(i);
if((chr<48&&chr!=46&&chr!=45&&chr!=44)|| chr>57) return false; } return true; }}
This is in my tMap:
MyRoutines.isNumeric((Relational.ISNULL(row1.WagenparkNummer)?"a":row1.WagenparkNummer))?Integer.parseInt(row1.WagenparkNummer):0
I created the job with Talend 5.1.2.r90681 and tested it on Windows 7.0. A random record says '001554' in SQL. After conversion the field is saved as 1554 in the TMS database.
I exported the job and extracted the zip file on a Linux system. (Nothing special, I have done this before for around 40 jobs).
And now the strange thing: After running the job on Linux, the same record is converted to 15 instead of 1554.
Why???
Edit:
It only effects records with leading zero's. Records without leading zero's are converted in the correct way.
(Example given: '002534' is converted wrongly to 25. '2534' is converted to 2534.)
Screenshots: First subjob clears the output database. The second subjob retrieves information from a SQL server, convert some fields and store the result in the output database Kewill.