[
https://issues.jboss.org/browse/TEIID-2621?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2621.
-----------------------------------
Resolution: Done
There was very little here that could be done easily. The improvements made were to infer
the byte position of the failing conversion in InputStreamReader logic, which will be
visible in the full stacktrace - otherwise the conversion error can happen anywhere in the
conversion buffer which means that the line/column known to texttablenode isn't truly
accurate. Also corrected the distinction that the cause of a TeiidSQLException is not the
first chained exception.
improve texttable error messages
--------------------------------
Key: TEIID-2621
URL:
https://issues.jboss.org/browse/TEIID-2621
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
Not all exceptions from texttable report the line number. Additionally we should be
consistent about reporting a 1 based line number and a column number would be useful as
well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira