[jira] [Resolved] (CARBONDATA-1936) Bad Record logger is not working properly in Carbon Partition

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

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

Jacky Li resolved CARBONDATA-1936.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

> Bad Record logger is not working properly in Carbon Partition
> -------------------------------------------------------------
>
>                 Key: CARBONDATA-1936
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1936
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Ravindra Pesala
>            Priority: Minor
>             Fix For: 1.3.0
>
>         Attachments: test.csv.csv
>
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> Bad records are not logging and the load is always success irrespective of bad records are present. 
> : CREATE  TABLE IF NOT EXISTS emp1 (emp_no int,ename string,job string,mgr_id int,date_of_joining string,salary int,bonus int) partitioned by (dept_no int) STORED BY 'org.apache.carbondata.format' ;
> 2: LOAD DATA INPATH 'hdfs://hacluster/user/test/emp.csv' overwrite INTO TABLE emp1 OPTIONS('DELIMITER'=',', 'QUOTECHAR'= '\');
> 3: Observe that load is failing
> 4: LOAD DATA INPATH 'hdfs://hacluster/user/test/emp.csv' overwrite INTO TABLE emp1 OPTIONS('DELIMITER'=',', 'QUOTECHAR'= '\','BAD_RECORDS_ACTION'='FORCE');
> 5: Observe that load is success when 'BAD_RECORDS_ACTION'='FORCE' is given in load command
> 6: Also observe that same load is suucess in a table without partition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)