You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2021/11/10 01:35:00 UTC

[jira] [Reopened] (IOTDB-1938) compare timeseries when loading tsfile

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

Jialin Qiao reopened IOTDB-1938:
--------------------------------

> compare timeseries when loading tsfile
> --------------------------------------
>
>                 Key: IOTDB-1938
>                 URL: https://issues.apache.org/jira/browse/IOTDB-1938
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: Core/Server
>    Affects Versions: master branch, 0.12.2
>            Reporter: yusicheng
>            Assignee: yusicheng
>            Priority: Major
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> Now:
>   Every device's start time and end time will be compared to determine which folder(seq/unseq) the loading tsfile belongs to.
>   But sometimes, a device which two tsfiles both have may have different measurements, while the device has the same start time and end time, and the loading tsfile will be loaded in unseq folder.
> Should:
>   We should consider two tsfiles is not overlap with each other, because two tsfiles have different timeseries. Obviously, the time of compare every timeseries in loading tsfile is much less than the time of unseq compaction.



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