[ 
https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455589#comment-15455589
 ] 

ASF GitHub Bot commented on TRAFODION-1676:
-------------------------------------------

GitHub user traflm opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/684

    [TRAFODION-1676] rework, fix executor regression test022 failures

    rework of the JIRA, in previous code, it get display string length using 
strlen(), but the srcData is not null-terminated for sure, so it will randomly 
get some unknown content.
    And also refactor the previous code for better coding rule.
    This should address the sql regression failure of executor/TEST022.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/traflm/incubator-trafodion TRAFODION-1676

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/684.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 #684
    
----
commit 758bc3828fadcb01633b3ac84d36ba9ead2599bf
Author: Liu Ming <lium...@apache.org>
Date:   2016-09-01T14:35:49Z

    [TRAFODION-1676] rework, fix executor regression test022 failures

----


> 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
>             Fix For: 2.1-incubating
>
>
> 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)

Reply via email to