[jira] [Resolved] (CARBONDATA-4040) Data mismatch incase of compaction failure and retry success

Posted by Akash R Nilugal (Jira) on Dec 14, 2020; 7:39am
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/jira-Resolved-CARBONDATA-4040-Data-mismatch-incase-of-compaction-failure-and-retry-success-tp104682.html


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

Ajantha Bhat resolved CARBONDATA-4040.
--------------------------------------
    Fix Version/s: 2.2.0
       Resolution: Fixed

https://github.com/apache/carbondata/pull/3999

> Data mismatch incase of compaction failure and retry success
> ------------------------------------------------------------
>
>                 Key: CARBONDATA-4040
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-4040
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Ajantha Bhat
>            Assignee: Ajantha Bhat
>            Priority: Major
>             Fix For: 2.2.0
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> For compaction we don't register inprogress segment. so, when unable to get table status lock. compaction can fail. That time compaction partial segment need to be cleaned. If the partial segment is failed to cleanup due to unable to get lock or IO issues. When the user retries the compaction. carbon uses same segment id. so while writing the segment file for new compaction. list only the files mapping to the current compaction, not all the files which contains stale files.

--
This message was sent by Atlassian Jira
(v8.3.4#803005)