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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Akash R Nilugal (Jira)

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

Ajantha Bhat updated CARBONDATA-4040:
-------------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.1.1

> 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.1.1
>
>          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)