Strange Behaviour of Jasper ETL

[umair]

I am using Jasper ETL 2.3.1.

The operation i want to perform is very simple.

Read from a CSV file and populate the corresponding record in MySQL Table, Country.

 

The structure of Table 'Country' is:

 

Country_Id

Country_Name

MCC

CC

 

I loaed a tFileInputDelimited and tMySQLInput component. I attached the two using a TMAP Component.

When i ran the ETL tool, i received the following error:

 

Exception in component tMysqlOutput_3

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'colname' in 'field list'

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at com.mysql.jdbc.Util.handleNewInstance(Util.java:353)

at com.mysql.jdbc.Util.getInstance(Util.java:336)

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1031)

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:957)

at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2938)

at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1601)

at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1710)

at com.mysql.jdbc.Connection.execSQL(Connection.java:2436)

at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1402)

at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1694)

at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1608)

at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1593)

at sample_etl.testjob_inkfish.TestJob_InkFish.tFileInputDelimited_1Process(TestJob_InkFish.java:453)

at sample_etl.testjob_inkfish.TestJob_InkFish.runJobInTOS(TestJob_InkFish.java:678)

at sample_etl.testjob_inkfish.TestJob_InkFish.main(TestJob_InkFish.java:597)

 

 

This was strange.

There was no column 'colname' in my DB.

 

 

I tried debugging the problem and saw that when i changed the column name 'Country_Name' to anything other then 'Country_Name', it worked fine without any warnings or errors.

The problem only occured when the DB field was named 'Country_Name'.

I changed it to 'Country_Name2' and it worked fine.

 

This is really strange. Can anyone help me in realizing the problem?

 

Can it be a bug?