carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohammad Shahid Khan (JIRA)" <>
Subject [jira] [Commented] (CARBONDATA-634) Load Query options invalid values are not consistent behaviour.
Date Wed, 18 Jan 2017 05:54:27 GMT


Mohammad Shahid Khan commented on CARBONDATA-634:

As of now if user is setting wrong option for BAD_RECORDS_ACTION, the system takes the default
value as force.
Which is not correct behavior, as the force load can change the actual data.
By default if no value is set by default  BAD_RECORDS_ACTION will be initialized with FORCE.
But if the value for BAD_RECORDS_ACTION  is set then the the value should be validated.

> Load Query options invalid values are not consistent behaviour. 
> ----------------------------------------------------------------
>                 Key: CARBONDATA-634
>                 URL:
>             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
>         Attachments: 2000_UniqData.csv
> 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
>  select *   from Dataload_uniqdata limit 10 ;

This message was sent by Atlassian JIRA

View raw message