topic Re: [resolved] tMySQLOutput creates table but does not insert rows in Talend Studio

[resolved] tMySQLOutput creates table but does not insert rows

benu — Sat, 16 Nov 2024 11:33:01 GMT

I've got a simple job that extracts 7 rows using a tSalesforceInput and sends that data to a tMySQLOutput. I have the tMySQLOutput set to "Drop table if exists and create" and "Action on data" is "Insert". The chain of components is like this:
tSalesforceConnection --OnSubjobOk--> tMySQLConnection --OnSubjobOk--> tSalesforceInput --main--> tMySQLOutput --main--> tLogRow
The connections succeed. The Salesforce query succeeds. The table gets created in the MySQL DB. However, the rows do not get inserted. I also get all rows output to the tLogRow.
I've checked permissions for the MySQL user account - they seem correct. They're obviously good enough to create a table, and I see I've granted all the other DML rights, too (INSERT, DELETE, EXECUTE, etc. - all of them). I've also executed an insert using the MySQLWorkbench client, which succeeded - from the same client workstation upon which I run the Talend job in-question.
I'm stumped - any suggestions out there? Thanks in-advance.
-Ben

Re: [resolved] tMySQLOutput creates table but does not insert rows

benu — Thu, 07 Aug 2014 23:49:30 GMT

Solved. This was pretty damn infuriating. It turned out to be the "Auto Commit" setting on the tMySQLConnection component. It's off by default, and if you don't set it, any components that use the connection will not commit their transactions.
There went a whole day of troubleshooting. Anyway, glad I found this post:
https://community.talend.com/t5/Design-and-Development/tMysqlOutput-doesn-t-populate-table-if-using-existing-connection/td-p/115934
Thanks zootal and alevy!
-Ben

Re: [resolved] tMySQLOutput creates table but does not insert rows

Anonymous — Thu, 18 Sep 2014 21:24:54 GMT

Thanks, I had the exact same problem, and this solved it.

Re: [resolved] tMySQLOutput creates table but does not insert rows

Anonymous — Mon, 06 Jul 2015 11:53:20 GMT

Thanks you all,
I faced the same issue and it's resolved now.