[jira] [Closed] (IOTDB-421) Problem about merge
[ https://issues.apache.org/jira/browse/IOTDB-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-421. - Fix Version/s: 0.10.0-SNAPSHOT Resolution: Fixed > Problem about merge > --- > > Key: IOTDB-421 > URL: https://issues.apache.org/jira/browse/IOTDB-421 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Kaifeng Xue >Priority: Major > Labels: pull-request-available > Fix For: 0.10.0-SNAPSHOT > > Time Spent: 0.5h > Remaining Estimate: 0h > > After dividing storage groups by time partition, merge part contains a > potential bug about merging different partition's data into one partition. > Reproduce method: > Using benchmark to insert data for 2 hours. And query like this: > select s_0 from root.group_0.d_0 > The result are not sorted by timestamps -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-422) Close current files before merge.
[ https://issues.apache.org/jira/browse/IOTDB-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-422. - Resolution: Fixed > Close current files before merge. > - > > Key: IOTDB-422 > URL: https://issues.apache.org/jira/browse/IOTDB-422 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.10.0-SNAPSHOT >Reporter: Tian Jiang >Priority: Major > Labels: merge, pull-request-available > Fix For: 0.10.0-SNAPSHOT > > Time Spent: 40m > Remaining Estimate: 0h > > If some unseq file overlaps the unsealed seq file and a merge is triggered, > the overlapped data may not be able to be merged into the right file. > To resolve this, the files should be closed before a merge starts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-396) New query clause: disable align
[ https://issues.apache.org/jira/browse/IOTDB-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-396. - Fix Version/s: 0.10.0-SNAPSHOT Resolution: Fixed > New query clause: disable align > --- > > Key: IOTDB-396 > URL: https://issues.apache.org/jira/browse/IOTDB-396 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Jialin Qiao >Priority: Major > Labels: pull-request-available > Fix For: 0.10.0-SNAPSHOT > > Time Spent: 40m > Remaining Estimate: 0h > > After parallel querying: [https://github.com/apache/incubator-iotdb/pull/684] > , the query speed has bound by the alignment of time across time series. > Therefore, it's better to supply a more efficient interface that does not > align time series by time. Which could be implemented by adding a new clause: > disable align. > > If users select N time series, the result is: > time1, value1, time2, value2, ..., timeN, valueN -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-422) Close current files before merge.
Tian Jiang created IOTDB-422: Summary: Close current files before merge. Key: IOTDB-422 URL: https://issues.apache.org/jira/browse/IOTDB-422 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.10.0-SNAPSHOT Reporter: Tian Jiang Fix For: 0.10.0-SNAPSHOT If some unseq file overlaps the unsealed seq file and a merge is triggered, the overlapped data may not be able to be merged into the right file. To resolve this, the files should be closed before a merge starts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
??????[jira] [Created] (IOTDB-421) Problem about merge
Hi~ I'm working on this issue. Please feel free to contact with me :) -- -- ??: "Yuan Tian (Jira)"https://issues.apache.org/jira/browse/IOTDB-421 Project: Apache IoTDB Issue Type: Bug Reporter: Kaifeng Xue After dividing storage groups by time partition, merge part contains a potential bug about merging different partition's data into one partition. Reproduce method: Using benchmark to insert data for 2 hours. And query like this: select s_0 from root.group_0.d_0 The result are not sorted by timestamps -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-421) Problem about merge
Kaifeng Xue created IOTDB-421: - Summary: Problem about merge Key: IOTDB-421 URL: https://issues.apache.org/jira/browse/IOTDB-421 Project: Apache IoTDB Issue Type: Bug Reporter: Kaifeng Xue After dividing storage groups by time partition, merge part contains a potential bug about merging different partition's data into one partition. Reproduce method: Using benchmark to insert data for 2 hours. And query like this: select s_0 from root.group_0.d_0 The result are not sorted by timestamps -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] When Release 0.10.0
Hi, > Refer to the temporary release note for `0.10.0-SNAPSHOT`, auto-generated by JIRA [1]. So we should not call the fixed version of an issue as "0.10.0-SNAPSHOT" (and not "master branch"), it should be "0.10.0". Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lei Rui 于2020年1月14日周二 上午10:20写道： > Hi, > > > It has been almost two months since the release tag of `release/0.9.0` was > created on Nov 23, 2019. > > > 1. New changes that have taken place: > Refer to the temporary release note for `0.10.0-SNAPSHOT`, auto-generated > by JIRA [1]. > (about 16 bug fixes, 4 new features, 13 improvements) > > > 2. Upcoming new changes: > As far as I know, the develop team has been working towards two directions > recently: > 1. the distributed version of IoTDB > 2. the refactor of both physical design and query processing > > > Shall we withhold the release of 0.10.0 until the two upcoming changes are > finished? > What do you think? > > > > Regards, > Lei Rui > > > [1] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322720&version=12346616 > >
