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

Ravindra Pesala resolved CARBONDATA-634.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating

> Load Query options invalid values are not consistent behaviour. 
> ----------------------------------------------------------------
>
>                 Key: CARBONDATA-634
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-634
>             Project: CarbonData
>          Issue Type: Bug
>          Components: data-load
>    Affects Versions: 1.0.0-incubating
>         Environment: spark-1.6
>            Reporter: Payal
>            Assignee: Mohammad Shahid Khan
>            Priority: Minor
>             Fix For: 1.0.0-incubating
>
>         Attachments: 2000_UniqData.csv
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> If we pass invalid keyword in ('BAD_RECORDS_ACTION'='FAIL'), its behaves like 
> default('BAD_RECORDS_ACTION'='FORCE') , here we require some error message 
> instead of default behavior.  
> Query
> CREATE TABLE Dataload_uniqdata1 (CUST_ID int,CUST_NAME 
> String,ACTIVE_EMUI_VERSION string, DOB timestamp, DOJ timestamp, 
> BIGINT_COLUMN1 bigint,BIGINT_COLUMN2 bigint,DECIMAL_COLUMN1 decimal(30,10), 
> DECIMAL_COLUMN2 decimal(36,10),Double_COLUMN1 double, Double_COLUMN2 
> double,INTEGER_COLUMN1 int) STORED BY 'org.apache.carbondata.format';
>  LOAD DATA INPATH 
> 'hdfs://hadoop-master:54311/data/uniqdata/2000_UniqData.csv' into table 
> Dataload_uniqdata OPTIONS('DELIMITER'=',' , 
> 'QUOTECHAR'='"','BAD_RECORDS_LOGGER_ENABLE'='TRUE', 
> 'BAD_RECORDS_ACTION'='FAIL','FILEHEADER'='CUST_ID,CUST_NAME,ACTIVE_EMUI_VERSION,DOB,DOJ,BIGINT_COLUMN1,BIGINT_COLUMN2,DECIMAL_COLUMN1,DECIMAL_COLUMN2,Double_COLUMN1,Double_COLUMN2,INTEGER_COLUMN1');
>  select *   from Dataload_uniqdata limit 10 ;



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

Reply via email to