[
https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355174#comment-15355174
]
ASF GitHub Bot commented on TRAFODION-1676:
-------------------------------------------
GitHub user traflm opened a pull request:
https://github.com/apache/incubator-trafodion/pull/564
[TRAFODION-1676]support better runtime error message when a SQL funct…
…ion meet fital error
During normal query execution, the error message of many functions doesn't
contain any clue about what data cause the error, making it rather difficult to
find the offending source. Especially difficult when doing bulkload where
millions of rows are about to be loaded, if there are some bad value, it is
extremely hard to find them.
This PR enhance error messages for these SQL Errors:
EXE_CONVERTTIMESTAMP_ERROR = 8405,
EXE_JULIANTIMESTAMP_ERROR = 8407,
EXE_CONVERT_STRING_ERROR = 8413
EXE_CONVERT_DATETIME_ERROR = 8415,
By displaying the offending source data content, for CONVERT_STRING_ERROR,
because it always contains multi-byte character, so display the data in HEX
mode.
This was minor issue, but become high recently because it is really very
hard to fix source data if error msg cannot tell the user enough info. With
this change, the user can search for bad value in source more easier.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/traflm/incubator-trafodion TRAFODION-2046-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/564.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #564
----
commit 5b8eba5598f8e45339a1ba649cd2214117ed7381
Author: Liu Ming <[email protected]>
Date: 2016-06-29T12:47:38Z
[TRAFODION-1676]support better runtime error message when a SQL function
meet fital error
----
> support better runtime error message when a SQL function meet fital error
> -------------------------------------------------------------------------
>
> Key: TRAFODION-1676
> URL: https://issues.apache.org/jira/browse/TRAFODION-1676
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-exe
> Reporter: liu ming
> Assignee: liu ming
> Priority: Minor
>
> A sql contains some SQL function, for example UPPER(), when the input data of
> UPPER() contains invalid data, UPPER() will fail. In this case, the whole
> query abort, and the error message cannot tell which row has invalid data, so
> it is very hard to fix the problem.
> It will be good to have row id or the real value of the error row in the
> error message to help trouble shooting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
