[
https://issues.jboss.org/browse/TEIID-3004?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3004:
---------------------------------------
Could it be a too long string that got cut from the webservice
translator?
We won't proactively truncate content, but that can happen sometimes with proxies or
other middle men.
You'll need to see what the raw text that Teiid is seeing looks like on line 16,161 -
for example by just selecting and inspecting the clob that you form getting.
The exception occurs when we see something like:
x y"...
Where we encounter the character y in between the delimiter ' ' and the "
qualifier.
TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace
character found between the qualifier and the delimiter in text line 16,161 in Unknown.
SQLState: TEIID30183
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-3004
URL:
https://issues.jboss.org/browse/TEIID-3004
Project: Teiid
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 8.8
Reporter: luca gioppo
Assignee: Steven Hawkins
Priority: Minor
On the same use case of TEIID30181 I now got the error in object:
TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between
the qualifier and the delimiter in text line 16,161 in Unknown.
SQLState: TEIID30183
the row should be:
istsc_pgee021002 Direzione Didattica Statale "Franco Rasetti" Castiglione del
Lago ANTONIETTA MANNUCCI 06061 PG Umbria
www.dirclago.it Via Carducci, 25 Dirigente
Scolastico Istituti di Istruzione Statale di Ogni Ordine e Grado Pubbliche
Amministrazioni S 80005650546 pgee021002(a)pec.istruzione.it pec pgee021002(a)istruzione.it altro null null null null null null 0
the only difference I find between the previous rows that passed without problems is that
a field has double quote in its content.
The delimiter is tabulation so there should not be any problem.
Could it be this the problem and how to solve it?
Thanks
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)