You are not logged in.
Announcement
Unanswered posts
|
Pages: 1

Hi folks,
some x-files' style bug here
Probably the strangest problem I'm periodically running into while using Talend is the one depicted in an image being attached.
Very simple script - tmyslinput->tmap->tmysqloutput. Sometimes, after running it, it does stop at a certain row (always the same row,
as in this picture - row 1345) and simply does nothing - neither produces an error, nor continues inserting rows, nothing, just halts and waits
until i have to kill it, even though there are much more rows in the input table.
The next row following row after the one which is last shown as being inserted, in this case - 1346 after 1345, always contains text with double
quotes being used in it. After removing double quotes from the row 1346, the script works neatly.
The same happens using the tlogrow component instead of tmysqloutput as well, meaning that the bug
happens somewhere in either tmysqlinput or tmap component.
source mysql table has DEFAULT CHARSET=utf8 COLLATE=utf8_bin being set, and i use the following settings for the tmysqlinput:
"noDatetimeStringSync=true&useUnicode=yes&characterEncoding=UTF-8" as the "additional jdbc parameters" (guess tried it with only
"noDatetimeStringSync=true", no help) and the "utf-8" as the "encoding type".
Once awhile ago, i've managed to solve it using row1.conent==null?"Empty row": StringHandling.EREPLACE(row1.content, ""+DataOperation.CHAR(34), "") as tmap
expression, but now it doesn't help (there's a chance that it's not the exact expression i've used than, but i guess that's the right one).
1st question: Maybe anyone has ran into the same/similar situation and managed to find a way to solve it?
2nd question: I know there can be hell a lot of possible problems connected with string encodings, so, probably even more important question is, how should i debug these type of bugs?
thanks for listening,
have a nice day,
jamesm
Offline
Pages: 1