[
https://issues.apache.org/jira/browse/CARBONDATA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akash R Nilugal updated CARBONDATA-2021:
----------------------------------------
Description:
when delete is success and update is failed while writing status file then a stale carbon data file is created.
so removing that file on clean up . and also not considering that one during query.
when the update operation is running and the user stops it abruptly,
then the carbon data file will be remained in the store .
so extra data is coming.
during the next update the clean up of the files need to be handled.
and in query also new data file should be excluded.
was:
when delete is success and update is failed while writing status file then a stale carbon data file is created.
so removing that file on clean up . and also not considering that one during query.
when the update operation is running and the user stops it abruptly,
then the carbon data file will be remained in the store .
so extra data is coming.
during the next update the clean up of the files need to be handled.
and in query also new data file should be excluded.
CREATE TABLE uniqdata_hive (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)ROW FORMAT DELIMITED FIELDS TERMINATED BY ',';
insert into uniqdata_int_string partition(cust_id='1',cust_name='CUST_NAME_00002') select * from uniqdata_hive limit 10;
> when delete is success and update is failed while writing status file then a stale carbon data file is created.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CARBONDATA-2021
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-2021> Project: CarbonData
> Issue Type: Bug
> Reporter: Akash R Nilugal
> Assignee: Akash R Nilugal
> Priority: Minor
> Time Spent: 3h
> Remaining Estimate: 0h
>
> when delete is success and update is failed while writing status file then a stale carbon data file is created.
> so removing that file on clean up . and also not considering that one during query.
> when the update operation is running and the user stops it abruptly,
> then the carbon data file will be remained in the store .
> so extra data is coming.
> during the next update the clean up of the files need to be handled.
> and in query also new data file should be excluded.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
