[jira] [Closed] (ASTERIXDB-2379) Inconsistent naming for LSM Component timestamps

["Chen Luo (JIRA)" <ji...@apache.org>]

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

Chen Luo closed ASTERIXDB-2379.
-------------------------------
    Resolution: Not A Problem

> Inconsistent naming for LSM Component timestamps
> ------------------------------------------------
>
>                 Key: ASTERIXDB-2379
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2379
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: STO - Storage
>            Reporter: Chen Luo
>            Priority: Major
>
> The current naming of LSM components are inconsistent. AbstractLSMIndexFileManager.getComponentStartTime/getComponentEndTime assumes a component is named as "beginTS-endTS". However, physically a component is named as "endTS-beginTS". This leads to recovery problems because certain valid components could be erroneously deleted because of index checkpointing check.
> The problem is caused by merge operation. For example, in LSMBTree.getMergeFileReferences, firstComponent is actually newer than lastComponent, which breaks the assumption of time range.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)