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

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

GitHub user selvaganesang opened a pull request:

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

    [TRAFODION-2351] Bulk load with log error rows enhancements

    Load with log error rows won't work if there are multiple ranges
    involved in the hdfs scan. The hdfs log file is closed when the
    first range of hdfs scan is done.  The error rows in the subsequent
    ranges will not be logged. Instead an SQL warning is generated for
    each process.  When these warnings are shipped from ESPs to master,
    ESP dumps core.
    
    Added tests to test load with log error rows and continue on error

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

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
trafodion-2351_5

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

    https://github.com/apache/incubator-trafodion/pull/931.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 #931
    
----

----


> Bulk load with log error rows enhancements
> ------------------------------------------
>
>                 Key: TRAFODION-2351
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2351
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-exe
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>
> Bulk load needs the following enhancements
> 1) Load with log error rows misses out some error rows being logged
> 2) Load with log error rows need to report if there are any error rows
> 3) Load with log error rows need to report where the error rows are logged



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to