Exception in component tMysqlOutput_1 com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Row size too large.

[DM_J]

Hello,

I am getting this error when I want to add a timestamp field to a table from the flow in Talend. By the flow I mean I have the data and I don't want to add a new timestamp data like using the Advanced Setting of tMysqlOutput. (Note: I don't get any error when I want to add a new timestamp by Advanced Setting)

For example, I have two tables both have a timestamp field. I merged them and cleaned them. I stored the clean data in a new table with tMySqlOutput without any errors but when I wanted to save the timestamp of these two tables in the new table I got the error.

I checked the data with tLog and it seems OK: 2019-02-04 11:45:07 AM

I also changed the DBType from VARCHAR to TEXT in the output of tMySqlOutput and yet no success.

I appreciate any help.

As Mr, Vapukov asked here is the design

Here, I didn't add the timestamp field in the second tMap, and there is no error:

But when I add the timestamp field in that tMap I am getting the error.

Timestamp comes from these two tables, both of them have a timestamp with a not null value

Here is tMySQLoutput

So I don't know exactly what this problem is it an OS issue? The config is Linux Ubuntu 18.04 LTS, Talend 7, Java 1.8

[vapukov]

hi,

it is hard to guess without seeing your design

- what structure?

- why you use varchar or text for timestamp?

- etc

[DM_J]

Hello,

 I updated my question hope now it is more clear to you.

Thanks

[vapukov]

---

@DM_J wrote:

Hello,

 I updated my question hope now it is more clear to you.

Thanks

---

Hi,

thank  you, but the answer is "No!" 🙂

I not interesting - how is your design looks

but how looks tMap where you add timestamp, and how looks structure in tDBOutput component (maybe after we will need more information)

[DM_J]

Hello,

 I added what you asked hopefully

[vapukov]

ok,

let start to cleanup!

do you know any person with full name length 65000 character?

I for all my long life don't meet any of them! 🙂 

same as I do not know any city longer than 50, ok 100 characters!

even if you have something like:

let do all proper from begin:

- define realistic and not too big values for all columns

- do not leave empty lenght like for member_id and first and last names

- do not use text for timestamp, max varchar(29), but much better - datetime, why store timestamp as string? no one real reason for this

something like:

• APMSQ_ID - VARCHAR(36)
• FullName - varchar(150)
• member_id - varchar(36)
• first_name - varchar(50)
• .....
• timestamp - datetime

to avoid potential problems - always select trim all columns in advanced settings for input component

let do this