You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "周沛辰 (Jira)" <ji...@apache.org> on 2022/03/09 07:58:00 UTC

[jira] [Commented] (IOTDB-2682) Query more data which has been deleted in compaction from 0.12.5

    [ https://issues.apache.org/jira/browse/IOTDB-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503363#comment-17503363 ] 

周沛辰 commented on IOTDB-2682:
----------------------------

Based on the existing inner compaction process in 0.12.5, this bug cannot be fixed. The reason is: The new deletion in inner comapction in 0.12 is written to the mods file of the source file. And after 0.12 merges and generates the target file, the process is to read the deletion of all the source files, then delete the mods files of the source files, and finally write deletions into the target mods file.

1) Assuming that after deleting the mods files of the source files, it is interrupted before writing to the target mods file, at this time, the deleted data will still be queried in recovery at 0.13.

2) Even if the mods files of the source files exist, we can't distinguish which is new deletion and which is old deletion.

> Query more data which has been deleted in compaction from 0.12.5
> ----------------------------------------------------------------
>
>                 Key: IOTDB-2682
>                 URL: https://issues.apache.org/jira/browse/IOTDB-2682
>             Project: Apache IoTDB
>          Issue Type: Bug
>            Reporter: 周沛辰
>            Assignee: 周沛辰
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.13.0
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> Delete data during the compaction in 0.12.5, then break it, and recover it at 0.13 will query all the data that has been deleted during the compaction in 0.12.5



--
This message was sent by Atlassian Jira
(v8.20.1#820001)