[CARBONDATA-634] Load Query options invalid values are not consistent behaviour.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0-incubating
• Fix Version/s: 1.0.0-incubating
• Component/s: data-load
• Environment: spark-1.6
• Assignee: Mohammad Shahid Khan
• Reporter: Payal
• Created: 13/Jan/17 09:48
• Updated: 19/Jan/17 10:04
• Resolved: 18/Jan/17 10:09

Description

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 ;

Issue Links

• links to: GitHub Pull Request #548