[jira] [Issue Comment Deleted] (TRAFODION-1489) odb can not log rejected records in badfile

["Yang Yang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TRAFODION-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Yang updated TRAFODION-1489:
---------------------------------
    Comment: was deleted

(was: This issue contains 2034. 
For example, when loading with ODB, and setting BatchSize=1000, i.e. submitting 1,000 rows per batch, a dirty batch will be lost when any data within that 1,000-row-batch is "dirty". 
For example, if col2 type=vchar(10), if col2 in any one row contains vchar longer than 10, the batch or the dirty row in that batch will be lost. 

A partner complained a similar issue, when they tried to load a table of 48.8M rows with ODB, 20K rows were lost without keeping a log. 

A similar problem is witnessed by Vito with "load with log error rows into". When a large number of rows are dirty, loading will crash.  So, they'll have to use "load with continue on error into" to avoid loading crashing.  This problem will be filed as another Jira item. )

> odb can not log rejected records in badfile 
> --------------------------------------------
>
>                 Key: TRAFODION-1489
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1489
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: db-utility-odb
>    Affects Versions: 2.0-incubating
>         Environment: trafodion build 20150828, odb build clients-20150821_0830
>            Reporter: Feng Qiang
>            Assignee: Rao Kakarlamudi
>
> While loading data from file into trafodion table, we have bad records in the source file. Add option :bad=badfile or :bad=+badfile in the load command, badfile was created but rejected records were not written in the file.



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